Tool-Kiem-Thu — Roadmap (after Phase 3 / Governance / B7)

Date: 2026-06-10. Supersedes the phase ordering implied in prior planning docs by inserting an explicit Phase 3.5 Birth/Governance Onboarding gate. KB-level planning authority.

Phase ledger & current position

Phase	Scope	Status
Phase 0	Authority Contract v0.1 (B/C/D/G/H sealed)	✅ complete
Phase 1	Reuse Extraction Map	✅ complete
Phase 2	Offline MVP read/report inspector (ip_dot_inspector)	✅ PASS
B4′	Deny-by-default sandbox attestation	✅ PASS (12/12)
Phase 3	FIX7 read/report pilot	✅ PASS
B7 (core)	Governed export-packet pipeline core	✅ PARTIAL (design + reference-validated; promotion deferred)
Phase 3.5	Birth/Governance Onboarding + Auto-Governance Audit	◀ CURRENT — closing now (BIRTH_GOVERNANCE_ONBOARDING_PASS_AUTO_SYSTEM_PARTIAL)
Phase 4	Call Contract (command run + exit codes) — the keystone	⛔ BLOCKED (Codex mandatory before build)
Phase 5	Re-run FIX7 via governed packet	⛔ blocked-on Phase 4 + B7 promotion
Phase 6	(optional) Codex / Evidence Review of accumulated evidence (B0‴)	⛔ owner disposition
Phase 7	Controlled pilot	⛔ blocked-on Phase 4/5 + D11

Exact current position: Phase 3.5 is being closed by this macro. Phase 4 is the next design increment (author the Call Contract design packet read-only, no build, no Codex — exactly as B7 was done), but it MAY NOT start until Phase 3.5 governance is current (it is, after this macro) and must respect the future-macro governance rule.

Phase 3.5 — definition (new)

• Purpose: ensure no object created by Phase 2/3/B4′/B7 (or any future phase) is orphaned/ungoverned before the system advances to Call Contract / gate consumer / KB writer / controlled pilot / production integration.
• Deliverables: object registry (md+json), orphan report, lifecycle/authority map, CI repo lifecycle, auto-system audit, auto-detection coverage matrix, taxonomy-gap report, future-macro rule, root-cause blocker packet, onboarding blocker, master report, this roadmap, checkpoint, index update.
• Exit criterion: 0 KB-governance-orphans; auto-system coverage audited + root-caused; future-macro rule written. Met.
• Standing requirement: Phase 3.5 must be re-run / extended whenever a later phase creates new objects (per the future-macro rule). It is a recurring gate, not a one-off.

B7 status after onboarding

B7 core remains PARTIAL. Governance now records: packet schema + export-step contract = design-authority (pending-promotion); named-query catalog = provisional-non-authority (B7-EXP-1); packet sample = evidence-only local. No promotion performed. B7-EXP-1/EXP-2(D9)/D10/D11 remain action-ready blockers.

Gates that cannot be bypassed

1. Call Contract (Phase 4) requires Codex before any build.
2. Gate consumer (D11) and KB writer (D10) are prohibited to build until owner+Codex authorize; until then reports stay decision_effect=NONE.
3. Catalog promotion (B7-EXP-1) required before any named-query is cited as authority.
4. Phase 3.5 governance must be current before each of the above — enforced by the future-macro rule.

Verdict

ROADMAP_UPDATED — Phase 3.5 inserted and marked current; Phase 4/5/6/7 sequenced with their blocking conditions; B7 post-onboarding status recorded.