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, generic Skill and Workflow templates, 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 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.

Project-wide roadmap

P0 — Close the active governed-write validation

• [x] Create the Looper A3 test specification.
• [x] Complete the governed Looper evidence write.
• [x] Create a separate immutable execution verification receipt.
• [x] Re-evaluate Governed Memory Update using both the specification and execution receipt.