Aevum Repository Index

Date: 2026-04-16

Purpose: Top-level repository map for PM, engineering control, onboarding, and documentation governance

Scope rule: High-level organization only

1. Repository Purpose

This repository is an iOS-first Aevum/MindTwin/Core prototype organized around a Swift app target plus a set of modular Swift packages. It also contains a large documentation estate that exceeds the codebase in strategic breadth.

Top-level practical reading order:

App shell and project config
Core packages and persistence
UI components and actual surfaces
Integrations and automation
Tests
Documentation estate

2. Top-Level Directory Map

Path	Type	Purpose	PM importance
---	---	---	---
`App/`	App source	iOS app entry point and app assets	Critical
`Widgets/`	App extension	Widget bundle and entry widgets	Medium
`Packages/`	Modular code	Core business logic, UI modules, persistence, integrations, ML	Critical
`Docs/`	Documentation estate	BRD, architecture, testing, release, security, operations	Critical
`core.xcodeproj/`	Xcode metadata	Project, workspace, schemes	Critical
`project.yml`	Project definition	Declarative build/target definition	Critical
`README.md`	Project onboarding	Build/environment notes	High
`build/`	Derived local output	Built artifacts	Low
`Build Fix Logs/`	Build history	Local troubleshooting logs	Low
`Wireframes/`	Design reference	Visual concept artifacts	Medium
`Launch/`	Launch notes	Release/support notes	Medium
`Icons :Buttons/`	Design assets	Image/video resources	Low

3. Product Code Organization

3.1 App Layer

Primary responsibility:

app boot
onboarding gate
biometric gate
main tab shell
local API startup

Key files:

App/RAWDigistantApp.swift
App/Assets.xcassets/...

PM note:

This is the real app entry point and one of the most authoritative files for current-state truth.

3.2 Widget Layer

Primary responsibility:

quick voice launch
daily brief surface

Key files:

Widgets/RAWDigistantWidgets.swift
Widgets/QuickCaptureWidget.swift
Widgets/DailyBriefWidget.swift

PM note:

Widgets are real, but feature depth is uneven. Quick capture is more real than daily brief.

4. Package Index

4.1 `Packages/CoreMemory`

Purpose:

core local data model
SwiftData container
memory graph domain objects

Contains:

MemoryEntry
AevumEvent
persona/state/habit/legacy-related models
CoreMemoryManager

PM rating:

Structural importance: Very high
Current maturity: Medium

4.2 `Packages/IntelligenceEngine`

Purpose:

orchestration and intelligence flow
queue processing
local API
behavioral logic
daily/background processing

Contains:

BehaviourIntelligenceLayer
IntelligencePipeline
EventQueueActor
AevumLocalAPI
DailyProcessor
multiple cognition / routing / validation components

PM rating:

Structural importance: Very high
Current maturity: Mixed
Risk level: High

Reason:

This package contains many of the most ambitious claims and also several of the most important wiring gaps.

4.3 `Packages/UIComponents`

Purpose:

the real product surface library
dashboard, timeline, graph, settings, capture experiences

Key visible product files:

DashboardView.swift
LifeTimelineView.swift
KnowledgeMapView.swift
SettingsView.swift
CaptureSheet.swift
VoiceCaptureView.swift
DataIngestionView.swift
PhiSandboxView.swift

PM rating:

Structural importance: Very high
Current maturity: Medium

4.4 `Packages/CaptureEngine`

Purpose:

input capture support
import/OCR/calendar-adjacent capture support

Examples:

AppleCalendarSyncEngine.swift
OmnichannelImporter.swift

PM rating:

Structural importance: High
Current maturity: Medium-low

4.5 `Packages/CloudSyncEngine`

Purpose:

external sync/auth shell for calendars and workspaces

Reality:

currently largely stub/mock-backed

Key files:

OAuthProviders.swift
CalendarIntegrationManager.swift

PM rating:

Structural importance: High
Current maturity: Low

4.6 `Packages/PhiInferenceEngine`

Purpose:

local model handling
local inference runtime
model download management

PM rating:

Structural importance: High
Current maturity: Medium

4.7 `Packages/DecisionEngine`

Purpose:

decision node creation and logic

PM rating:

Structural importance: Medium
Current maturity: Medium

4.8 `Packages/MemoryGraphEngine`

Purpose:

graph abstraction and memory graph support

PM rating:

Structural importance: Medium
Current maturity: Medium-low

4.9 `Packages/SecurityLayer`

Purpose:

biometric access/security helpers

PM rating:

Structural importance: Medium
Current maturity: Medium

4.10 `Packages/ShortcutsIntegration`

Purpose:

App Intents / Shortcuts integration

Reality:

some real launch routing
some flows depend on pipeline boot

PM rating:

Structural importance: Medium
Current maturity: Medium-low

5. Documentation Estate Index

The documentation is large and should be treated as a separate managed system.

5.1 `Docs/00_Product_Requirements`

Purpose:

BRD and product requirement baseline
enterprise/system intent materials

Use for:

business framing
intended requirements

Do not use alone for:

current-state truth

5.2 `Docs/01_Core_Architecture`

Purpose:

architecture diagrams, handover documents, flow descriptions

Use for:

architectural intent
historical evolution

5.3 `Docs/02_Development_Architecture`

Purpose:

system diagrams and development-side architectural framing

5.4 `Docs/03_Testing_Quality_Assurance`

Purpose:

quality strategy
launch audits
test plans

PM note:

This folder is strategically useful, but current code reality does not yet match the implied test maturity.

5.5 `Docs/04_Compliance_Security`

Purpose:

privacy, security, audit, compliance material

5.6 `Docs/05_Quality_Engineering`

Purpose:

app store review justification
QE baseline materials

5.7 `Docs/06_Release_Control`

Purpose:

go/no-go and release baseline

5.8 `Docs/07_Enterprise_Strategy`

Purpose:

strategic capability and enterprise framing

5.9 `Docs/08_Enhancements`

Purpose:

roadmap and future enhancement tracking

5.10 `Docs/09_Operations_Maintenance`

Purpose:

operations baseline and telemetry documentation

6. Test Organization Index

6.1 Real test locations

Current test folders of note:

Packages/CoreMemory/Tests/...
Packages/DecisionEngine/Tests/...
Packages/IntelligenceEngine/Tests/...
Packages/CloudSyncEngine/Tests/...
Packages/SecurityLayer/Tests/...
Packages/MemoryGraphEngine/Tests/...

6.2 Weak test areas

App-level tests
UI automation
end-to-end test orchestration
multi-device validation

6.3 PM conclusion

Testing is package-centric, not product-centric.

7. Assets And Non-Code Areas

7.1 Visual/design references

Wireframes/
Icons :Buttons/

7.2 Release/build notes

Build Fix Logs/
Launch/

These are useful for context but should not be treated as source of truth over code and project configuration.

8. Highest-Level Organizational Model

For management purposes, the repository should be read in this hierarchy:

Tier 1: Source of current truth

project.yml
App/
Packages/
Widgets/

Tier 2: Validation of current truth

package tests
build artifacts/logs only as supporting evidence

Tier 3: Intended future-state and governance

Docs/

Tier 4: Visual/reference support

wireframes
icons
launch notes

9. PM Control Recommendation

Use this control order when making decisions:

Current running source and project config
Current module/test evidence
Then documentation intent

Do not reverse that order.

If documentation and code disagree, treat code as current reality and documentation as target intent until reconciled.

10. Suggested Governance Labels

For future document control, classify repo contents into these labels:

CURRENT_TRUTH
PARTIAL_IMPLEMENTATION
STUB_OR_MOCK
INTENDED_FUTURE_STATE
DESIGN_REFERENCE
RELEASE_SUPPORTING_ARTIFACT

This would immediately reduce scope confusion.

11. Final Index Summary

At the highest level of organization, this repository is:

a real iOS application codebase
supported by modular Swift packages
surrounded by a much larger strategic documentation system
currently more mature in architecture ambition than in end-to-end production wiring

That is the correct indexing baseline for project control.

Aevum Repository Index

1. Repository Purpose

2. Top-Level Directory Map

3. Product Code Organization

3.1 App Layer

3.2 Widget Layer

4. Package Index

4.1 Packages/CoreMemory

4.2 Packages/IntelligenceEngine

4.3 Packages/UIComponents

4.4 Packages/CaptureEngine

4.5 Packages/CloudSyncEngine

4.6 Packages/PhiInferenceEngine

4.7 Packages/DecisionEngine

4.8 Packages/MemoryGraphEngine

4.9 Packages/SecurityLayer

4.10 Packages/ShortcutsIntegration

5. Documentation Estate Index

5.1 Docs/00_Product_Requirements

5.2 Docs/01_Core_Architecture

5.3 Docs/02_Development_Architecture

5.4 Docs/03_Testing_Quality_Assurance

5.5 Docs/04_Compliance_Security

5.6 Docs/05_Quality_Engineering

5.7 Docs/06_Release_Control

5.8 Docs/07_Enterprise_Strategy

5.9 Docs/08_Enhancements

5.10 Docs/09_Operations_Maintenance

6. Test Organization Index

6.1 Real test locations

6.2 Weak test areas

6.3 PM conclusion

7. Assets And Non-Code Areas

7.1 Visual/design references

7.2 Release/build notes

8. Highest-Level Organizational Model

Tier 1: Source of current truth

Tier 2: Validation of current truth

Tier 3: Intended future-state and governance

Tier 4: Visual/reference support

9. PM Control Recommendation

10. Suggested Governance Labels

11. Final Index Summary

4.1 `Packages/CoreMemory`

4.2 `Packages/IntelligenceEngine`

4.3 `Packages/UIComponents`

4.4 `Packages/CaptureEngine`

4.5 `Packages/CloudSyncEngine`

4.6 `Packages/PhiInferenceEngine`

4.7 `Packages/DecisionEngine`

4.8 `Packages/MemoryGraphEngine`

4.9 `Packages/SecurityLayer`

4.10 `Packages/ShortcutsIntegration`

5.1 `Docs/00_Product_Requirements`

5.2 `Docs/01_Core_Architecture`

5.3 `Docs/02_Development_Architecture`

5.4 `Docs/03_Testing_Quality_Assurance`

5.5 `Docs/04_Compliance_Security`

5.6 `Docs/05_Quality_Engineering`

5.7 `Docs/06_Release_Control`

5.8 `Docs/07_Enterprise_Strategy`

5.9 `Docs/08_Enhancements`

5.10 `Docs/09_Operations_Maintenance`