Browser-ready version of the current-state PM baseline. This is grounded in the repository and documents what exists today, what is partial, and what is still conceptual.
Aevum today is a real iOS-first prototype with meaningful local code, local persistence, visible product surfaces, widgets, App Intents, and a partial localhost inference API. It is not yet the unified, deterministic, API-led, tri-surface Aevum Core described in the target architecture.
Dashboard voice/text input → BehaviourIntelligenceLayer → InstantProcessor → MemoryEngine → SwiftData.
Pipeline-dependent flows are implemented but the central IntelligencePipeline is not booted from the normal app startup path.
Internal prototype / alpha. Strong architecture ambition, uneven end-to-end delivery maturity.
Not ready for controlled public release without architectural reconciliation and test hardening.
| Question | Answer | Ground Truth |
|---|---|---|
| Aevum iPhone app exists? | YES | Real iOS app target exists. |
| Aevum iPad app exists? | YES | Same universal iOS app, not a distinct iPad product. |
| Aevum Mac app exists? | NO | No macOS app target found. |
| Local API running on localhost? | YES, PARTIAL | Listener on 127.0.0.1:8080 with one prompt endpoint. |
| Notion integration active via API? | NO | OAuth/session shell plus mock token and mock event injection. |
| Apple Shortcuts actively logging data? | NO | Intents exist, but direct logging depends on unbooted pipeline. |
| Siri integration working? | NO | Siri/App Intent exists, but is stub-level and not core-system wired. |
This is the strongest baseline path. User input in the dashboard goes through BehaviourIntelligenceLayer, then InstantProcessor, then MemoryEngine, then local SwiftData.
These flows enqueue into IntelligencePipeline. They are implemented, but not baseline-safe because the pipeline is not booted in normal app startup.
This is real. A shortcut sets a launch flag in UserDefaults and the app polls it to open voice capture.
| Storage Layer | Status | Notes |
|---|---|---|
| SwiftData / SQLite local store | Primary | Main local memory store. |
| UserDefaults / AppStorage | Active | Toggles, onboarding state, launch flags. |
| Local file storage | Active | Models, temp files, policy files. |
| Notion as storage backend | No | Not present as a real storage system. |
DailyProcessor background task code exists.Current API state is Partial API.
POST /aevum
Header: X-AEVUM-KEY
Body: {"prompt":"..."}
Response: {"response":"..."}
There is no current CRUD API for thoughts, tasks, goals, state, or debug/system validation endpoints.
| Device | Status | Reality |
|---|---|---|
| iPhone | Real | Primary current product surface. |
| iPad | Partial | Shared iOS app, not separately validated as a distinct product. |
| Mac | Missing | No real product target today. |
| Area | Status |
|---|---|
| Product vision readiness | High |
| Code reality readiness | Medium-low |
| Architecture coherence | Medium-low |
| Integration readiness | Low |
| Test readiness | Low |
| Release readiness | Low |
You currently have a serious prototype, not yet a finished operating system. The correct management move is still:
Reality -> documented baseline -> controlled scope -> stabilization -> selective build-out