<aside> 🚨

Current priority override — 2026-08-20: The active implementation order is now P0-1 Canonical State Reconciler → P0-2 Durable Execution History + one real Execution Room → P0-3 Code-Enforced Core Laws. P0-3 begins cross-cutting enforcement work during P0-1/P0-2. Historical roadmap items below remain preserved but do not outrank this current sequencing directive.

</aside>

Priority record: AIOS_P0_PRIORITY_STACK_01 — Canonical State, Execution Spine & Runtime Gates

Active P0 gates

• [x] P0-1 — RECONCILER_ACTIVE / 1.0 / MERGED / ACCEPTANCE_GREEN: cap:canonical-state-reconciler is Active at A0/read-only after the exact-head PR #53 merge. Automatic repair, projection rewrite, authority cutover, and implicit write authorization remain disabled. Activation receipt: AIOS ACTIVATION RECEIPT — cap:canonical-state-reconciler — 2026-08-20.
• [ ] P0-2 — ACTIVE / B02.1_MERGED / B02.2_MERGED / PROD_D1_VERIFY_BLOCKED / SITES_AUTH_REQUIRED: B02.1 merged through PR #54. B02.2 was repaired and merged through PR #55 to GitHub main at f7318032c159c1fed1b4f70d17042a227191db84; CI #228 passed Node 218/218, spatial 37/37, and the public-release boundary. External production probe PR #56 / CI #229 reached the production Sites hostname but received the ChatGPT Sites HTTP 401 sign-in interstitial before /api/workflow-executions. Existing repository tests stayed green; the production probe was the sole failing added test. No AIOS D1 headers were observed, no real execution was created, and production env.DB remains UNKNOWN rather than failed. Verification receipt: AIOS PROD VERIFICATION RECEIPT — P0-2 B02.2 Sites D1 Gate — 2026-08-20. Next gate is authenticated Sites access → require DURABLE_AVAILABLE / D1_DURABLE → create one real LIVE execution → force a fresh runtime boundary → read the exact execution back from D1 without process memory → B02.3 Execution Room 01. The legacy Notion+Drive system remains retained as continuity fallback: AIOS_REPOSITORY_CONTINUITY_FALLBACK_01 — Legacy System Backup.
• [ ] P0-3: Enforce scope isolation, authority resolution, SIMULATION/LIVE separation, provenance admission, and write authorization as runtime invariants.

Purpose

Canonical top-level development backlog for the complete memory system. This page controls sequencing and links to layer-owned backlogs. It does not replace canon, workflow definitions, project handoffs, or execution receipts.

Operating rule

• The master page tracks project-wide order, dependencies, and completion.
• Each layer backlog owns implementation details for that layer.
• A completed task requires a durable receipt or an authoritative state change, not merely a conversation claim.
• Project-domain work remains inside its project branch.
• Historical failures stay preserved and link to successful successors.

Current build focus

The MASON no-card, synthetic positive-candidate, deterministic accepted_noop, exact-replay, append-only delta, mixed-scope, and failed-verification branches are now validated. Continue with the first real positive-candidate ordinary run carrying an explicitly authorized durable delta, runtime context instrumentation, full workspace inventory, the Global control-plane mirror, and the complete STONE/MASON mirror. Do not authorize Drive cutover, general external write authority, canon promotion, or new Notion-only branch reparenting.

System reconciliation — 2026-08-03

Reviewed the hot AIOS current-state root, current-system map, Drive migration program, migration implementation backlog, MASON backlog, and Router/Capability backlog before changing completion state.

• Rolled up as complete: core Drive registry schemas; Drive shadow root, folder IDs, and registry file IDs; Looper workflow registration; Transition Manifest construction and dependent status synchronization.
• Still open: the music-generation → Udio A3 evidence-review gate, the first ordinary full-chain MASON run, production external destination-write handling, Drive templates and object inventory, the complete Skills/Workflows/governance mirror, and authority cutover.