Status: Planning authority for finishing the 9.0.0 fact-log line.
Date: 2026-09-25
Does not replace: FULL_FEATURE_TEST_PLAN.md, ENTERPRISE_GA_E2E_PLAN.md, CAPABILITY_INTEGRATED_USE_LEDGER.md, PERFORMANCE_QUALIFICATION.md, HARNESS_CONVERGENCE.md.

This roadmap answers one question: what sequence of evidence closes 9.0.0 under the repository's own definition of done.

1. The product delta is control, not features. 9.0.0 exists to make the immutable fact log the only coding control source (a3s-effect ingest_coding / resume_coding). Everything else is either support (a3s-vec 0.1.8 FTS) or out of cut ([Unreleased] Apofasi).
2. Labels are not completion. Version strings in Cargo.toml and a CHANGELOG section do not ship a channel. crates.io / npm / GitHub Release / docs line / tag do.
3. Digests bind to a commit. L5/L6 evidence on fa0a92ca does not cover later tip commits (TUI, ACL merge, model bind). An RC tip must re-earn L0–L6 (and L2 before a stable tag).
4. Correctness before latency; Core green before Harbor. L6 never rewrites Layer C oracles. Core CI never substitutes L7.
5. Two honest end states. Do not collapse them:
   • Channel release: multi-channel cut of the fact-log line with L0–L6 + L8 green, and either L7 receipts or a written product waiver naming which L7 rows are deferred.
   • Enterprise GA: every GA-board row true, including L7 close receipts (no silent waiver theater).
6. Do not invent green. Missing Harbor/CAR evidence stays open. A waiver is a product decision next to the tag, not an agent invention.

All must be true on one tagged commit RC:

Channel release DoD and L7 rows closed with receipts (waiver path forbidden for the GA claim). See ENTERPRISE_GA_E2E_PLAN §2.

Execute in order. Do not start a later phase while an earlier exit criterion fails, except where noted as parallel.

P0 Scope freeze
  → P1 Tip freeze + invariant audit
  → P2 Re-qualify L0–L6 + ledger on RC
  → P3 L2 + L8 pins
  → P4 L7 close OR product waiver          ⎫ parallel owners after P2 starts
  → P5 Multi-channel publish + docs        ⎭ requires P0–P3 + P4 disposition
  → P6 (optional) Enterprise GA remainder

Owner: product + Code maintainers
Actions:

1. Choose RC base: freeze current tip, or rewind/cut from fa0a92ca and land tip work as 9.0.x.
2. Confirm Apofasi stays out of 9.0.0 (default: yes).
3. Choose end-state A (channel release with L7 waiver) or B (wait for L7 / claim GA).

Exit: Written decision in CHANGELOG Notes (or adjacent release note) naming RC intent and L7 disposition path.

Owner: Code
Actions:

1. Stop merging non-blocker work onto the RC branch.
2. Audit against CHANGELOG invariants (C1): oneshot/timer absence, checkpoint non-authority, resume/tool-once, steer, empty-tool cap.
3. Add or confirm hermetics under core/src/agent_api/tests/fact_log.rs, core/tests/test_fact_log_real_llm.rs, and effect package suites.

Exit: Checklist of C1 invariants mapped to named tests; failures fixed on RC.

Owner: Code
Actions (serial where Live):

Exit: Every row cites RC SHA (not only fa0a92ca). FULL_FEATURE §13 L5/L6 cells updated to RC digests.

Owner: Code
Actions:

1. just f-table-cov (or documented llvm-cov recipe) → ALL_F_TABLE_KERNELS_GE_90.
2. Extend FULL_FEATURE §7 with 9.0.0 fact-log pins, at minimum:

3. Confirm prior §7 pins (8.5.x / 8.6.x / serve absence) still green on RC.

Exit: L2 FINAL present; §7 table includes 9.0.0 rows; pins green.

Owner: Harbor / Durable Memory / Cloud (external) + product for waiver
Fork:

Exit: Either filled receipt table or waiver committed next to the release notes. ENTERPRISE_GA board updated honestly.

Owner: release workflow
Prerequisites: P0–P3 exit + P4 disposition
Actions:

1. Tag v9.0.0 on RC; run release.yml (and language publish workflows).
2. Verify crates.io / npm / PyPI / Go module / GitHub Release all show 9.0.0 (do not claim multi-channel cut if one channel fails — see 8.5.10 lesson).
3. Archive website docs to docs/v9.0.0; update current-line pointers.
4. CHANGELOG Notes: full multi-channel cut list; Enterprise GA status exact.

Exit: External registries match tag; docs line exists; README “Prefer 9.0.0” accurate.

Only if P4 took the defer path or GA was never claimed.

Actions: Drive TB-QUAL1 / DM-PROD1 / CAR-01…05 to close; then update CHANGELOG / README / ENTERPRISE_GA board to achieved with receipt links. No new Core feature work required unless L7 fails expose a Code contract bug.

Exit: GA board all PASS with receipts.

Durations are capacity sketches, not SLAs.

P1 exit for this goal: Effect suite green on tip (recorded 2026-09-25: 40 tests passed). Code fact_log module tests must pass under local-code before L5.

1. Product path — locked to Enterprise GA above.
2. Code: keep RC tip freeze; land only blocker fixes.
3. Code: L0–L4 hermetic on tip → L5 Layer C → L6 Actions on tip SHA.
4. External: TB-QUAL1 full Harbor close; DM-PROD1 host pack; CAR-01/03/04/05 Cloud/Box receipts into HARNESS_CONVERGENCE (no invented green).
5. Release: multi-channel v9.0.0 only after L7 rows are Delivered.

This roadmap                 ──► sequenced closure of 9.0.0
FULL_FEATURE_TEST_PLAN       ──► L0–L8 train, §7 pins, §13/§14 status
ENTERPRISE_GA_E2E_PLAN       ──► GA board + L7 fork rules
CAPABILITY_INTEGRATED_USE    ──► E+E+I ledger for RC
PERFORMANCE_QUALIFICATION    ──► L6 digest sink
HARNESS_CONVERGENCE          ──► L7 receipt sink
a3s-effect README            ──► control-model axioms behind C1
CHANGELOG [9.0.0]            ──► shipped product claims

When a phase exits, update FULL_FEATURE §13, ENTERPRISE_GA §5–§6, the ledger date/SHA, and PERFORMANCE_QUALIFICATION in the same change set as the evidence. Do not mark this roadmap “complete” until §2.1 (or §2.2) is proven on the tagged commit.