Current State

Architecture v2 documentation baseline: Before new implementation, read web/engineering/architecture-v2/README.md. Phase-level completion statements remain subject to the new status ledger; local implementation presence is not production acceptance.

SnapshotCopy Anchor Link

Stable Phase 0 — Foundation: complete Stable Phase 1 — Core Platform: complete Stable Phase 1.5 — Public Web Product: complete Stable Phase 2 — Single Provider: complete Stable Phase 2.5 — Provider Generalization: complete Stable Phase 3 — Core Memory Substrate: complete Beta Phase 3.5 — Extraction & Context Assembly: under evidence review; provisional until the Architecture v2 ledger and linked exit evidence are reconciled Beta Phase 4 — Operator Platform & Multi-Provider: roadmap redesigned; Track P is the current prerequisite New Phase 4.5 — Intelligence Layer: planned New Phase 5 — Advanced Retrieval & Graph Memory: planned

Last updated: 2026-10-06 Branch: main at 393c8b7 (current public implementation baseline) Current focus: Issue #935: proposed Architecture v2 G0 documentation and contract freeze before new implementation Completed (recent): 3.5.F.3 Phase 3.5 exit audit; 3.5.F.2 ISO-MCP matrix; 3.5.F.1 learning-loop e2e; 4.C.5 streaming hardening baseline; 4.D.1 metadata overview (fc8735c); 4.D.2 metadata trace read slice (e4525e3)

Shipped Since Last UpdateCopy Anchor Link

• Phase 3.5 Track F 3.5.F.3: Benchmark sign-off + ADR index — gap register, summary
• Phase 3.5 Track F 3.5.F.2: Cross-tenant ISO-MCP isolation matrix (#759)
• Phase 3.5 Track F 3.5.F.1: Learning-loop e2e — make e2e-smoke-p3.5 (#752)
• Phase 3 Track E 3.E.5: Phase 3 exit audit — gap register, summary

What Ships TodayCopy Anchor Link

NextCopy Anchor Link

1. Accept the Architecture v2 G0 documentation and contract freeze tracked by #935: status ledger, authority matrix, contract registry, trust labels, and failure matrix.
2. Resolve P0 gaps before new service boundaries, provider adapters, write-capable tools, budget changes, or model integration.
3. Reclassify phase claims using source, test, benchmark, deployment-profile, and recovery evidence; then sequence G1–G11.

See Phase 3.5 and Phase 4.