Reference
Roadmap and gates
The documentation-first implementation sequence from G0 through G11.
The roadmap is a sequence of evidence gates, not a date-driven feature list. A gate closes only when the required artifacts, owners, and review are recorded.
Provisional Ledger class: provisional
Verified 2026-10-22Gate definitions are specified; most gates remain open
Gates
| Gate | Theme | Current status |
|---|---|---|
| G0 | Documentation and contract freeze | PROVISIONAL |
| G1 | Principal and tenant invariants | PROVISIONAL |
| G2 | Errors and idempotency | PROVISIONAL |
| G3 | Provider and admission | PROVISIONAL |
| G4 | Evidence MVP | PROVISIONAL |
| G5 | Request and streaming slice | PROVISIONAL |
| G6 | Typed memory and context | PROVISIONAL |
| G7 | Read-only operator and MCP | PROVISIONAL |
| G8 | Operations and recovery | PROVISIONAL |
| G9 | Governed side effects | PROPOSED |
| G10 | Advisory intelligence | PROPOSED |
| G11 | Deferred extensions | DEFERRED |
What each gate means
- G0 freezes authority, status, trust labels, dependencies, and ADRs before new boundaries or side effects.
- G1 proves principal propagation, authorization, RLS, cache/search/analytics isolation, and anti-enumeration.
- G2 proves error mappings and idempotency claim/finalize/replay/crash behavior.
- G3 proves provider manifests, token fit, reservations, limits, reconciliation, and no-provider-after-deny.
- G4 proves the evidence envelope, outbox, relay, dedupe/replay, redaction, retention, and restore.
- G5 proves one measured provider path, separate Responses semantics, stable errors, and an accepted latency budget.
- G6 proves typed memory provenance, trust, quarantine, operation status, deletion tombstones, and safe fallback.
- G7 proves the versioned operator API, Console, diagnostics, read-only MCP, descriptor hashes, and stdio policy.
- G8 proves profiles, backup/restore, migrations, drain, capacity, incidents, key rotation, and RPO/RTO.
- G9 would govern side effects with intent/receipts, approvals, egress controls, and isolated execution.
- G10 would allow advisory intelligence only after benchmark, pin, shadow, canary, rollback, and resource gates.
- G11 requires separate evidence and ADRs; it is not on the current dependency path.
Current baseline
Phases 0–3.5 are shipped locally. Phase 4 is in progress: Tracks A and B and context milestones C1–C3 are implemented locally; C4/C5, Track D beyond the first read slices, and the E gates are open. Track D milestones D3–D6 are deferred. Five G0 contract shapes were accepted as contract text on 2026-10-10; runtime seams remain provisional. No independent reviewer is named.
That means the roadmap is not “done at Phase 3.5.” It means the local substrate exists and the hard evidence work is still ahead.
Prohibited shortcuts
- Do not treat an accepted contract shape as an implemented runtime.
- Do not start a new service boundary before G0 exit.
- Do not enable a write-capable tool or governed side effect without G9.
- Do not claim production readiness from a gate definition.
- Do not replace an evidence gate with a release date.