Aevum Repository Index

Top-level repository map for PM control, engineering onboarding, and documentation governance. This page organizes the repo at the highest practical level so current truth is separated from documentation intent.

HTML Pack ยท 2026-04-18

Top-Level Directory Map

PathTypePurposePM Importance
App/App sourceMain iOS app shell and entry point.Critical
Widgets/ExtensionWidget bundle and widget entry surfaces.Medium
Packages/Modular codePersistence, UI, ML, orchestration, security, sync.Critical
Docs/Documentation estateRequirements, architecture, QA, release, compliance.Critical
core.xcodeproj/Xcode metadataProject and schemes.Critical
project.ymlBuild definitionDeclarative project source of truth.Critical
README.mdOnboardingBuild/environment guidance.High

Package Index

CoreMemory

SwiftData models, store container, core local graph state.

IntelligenceEngine

Behavior layer, queue processing, daily processor, local API, orchestration.

UIComponents

Dashboard, timeline, graph, settings, capture, sandbox and visible product surfaces.

CaptureEngine

Import, OCR, capture support, calendar capture support.

CloudSyncEngine

External auth/sync shell. Current maturity is low and stub-heavy.

PhiInferenceEngine

Local model orchestration and remote model download path.

Documentation Estate Index

Docs AreaPurposeUse Carefully
Docs/00_Product_RequirementsBRD and requirement intentGood for target state, not enough for current truth alone
Docs/01_Core_ArchitectureArchitecture handover and system framingMix of intent and architecture narrative
Docs/02_Development_ArchitectureSystem diagrams and engineering-side framingUseful for diagrams and intended structure
Docs/03_Testing_Quality_AssuranceQA and launch audit materialsCurrent code reality does not yet fully match these claims
Docs/04-09Security, QE, release, strategy, operationsGovernance and target-state support material

Highest-Level Organizational Model

Tier 1: Current Truth

project.yml, App/, Packages/, Widgets/

Tier 2: Validation

Package tests and build evidence.

Tier 3: Intended Future State

Docs/ architecture and requirement estate.

Tier 4: Reference Assets

Wireframes, icons, build-fix logs, release notes.

PM Rule

When code and documentation disagree, treat code and project configuration as current reality, and treat documentation as target intent until reconciled.