Incomex AI Portal
KB-5D20

04 — Implementation Track Map T0–T11 (2026-06-01)

9 min read Revision 1
one-roof-governanceimplementation-indextrack-mapt0-t11prerequisiteallowed-outputsforbidden-outputspass-criteriadesign-only2026-06-01

04 — Implementation Track Map (T0–T11)

This defines the tracks. It does not implement any of them. Each track produces design documents inside this package (doc 00 §0.7) plus, at most, read-only / BEGIN..ROLLBACK rehearsal. Production build is T11 only, after all upstream gates (doc 03) are approved.

Per track: Prerequisite · Allowed outputs · Forbidden outputs · Expected docs in this package · PASS criteria.

Dependency graph (text)

T0 (this index) ──┬─> T1 law-cleanup design ─────────────────┐
                  ├─> T2 OP-B owner packet ──> T5 SB-3 design ┤
                  ├─> T3 SB-1 design ──┐                      │
                  ├─> T4 SB-2 design ──┴─> T6 scanner design ─┤
                  ├─> T7 issue/event design ───────────────── ┤
                  ├─> T8 render/API design (needs C-5) ────── ┤
                  ├─> T9 Registries-Pivot integration design ─┤
                  └─> T10 IU integration design (needs OP-B+SB-3) ┘
                                                               │
                          all gates approved (doc 03 §3.5) ──> T11 production build

T1, T2, T3, T4, T7, T8, T9 are independent and may run in parallel. T5 waits on T2. T6 waits on T3+T4 (and concept GO). T10 waits on OP-B+SB-3. T11 waits on everything.

T0 — Source / index / control package (current mission)

  • Prerequisite: Round-4 concept patch complete.
  • Allowed outputs: this 16-doc package (index, source map, blockers, tracks, scaffolds, handoff, prompts, self-review).
  • Forbidden outputs: any technical design, any mutation beyond KB docs.
  • Expected docs: 00–15 of this package.
  • PASS: all 16 docs exist; future agents have one entrypoint; sources classified; blockers gate work; tracks clear; no implementation occurred.

T1 — Content-only law cleanup / registration-drift design (L-1/L-2)

  • Prerequisite: none beyond T0.
  • Allowed outputs: DRAFT law-text corrections; DRAFT normative_registry rows for Đ20/23/44/45; a ratification packet for the human enact phase; read-only survey.
  • Forbidden outputs: writing to normative_registry / law_catalog / governance_docs; enactment; version bump; status change; approval.
  • Expected docs: a T1-* doc set in this package (or extend scaffold 05–12 cross-refs); the DRAFT packet.
  • PASS: Đ36 version ambiguity resolved (recommendation); Đ45 leftover identified; Đ37 v3.3↔live-column reconciliation drafted; Đ20/23/44/45 DRAFT rows prepared; everything DRAFT, nothing written.

T2 — OP-B IU-owner decision packet

  • Prerequisite: T0; reads concept-canon doc 02 §3, Round-4 doc 05, IU foundation doc.
  • Allowed outputs: council decision packet; recommended owner-per-scope; C-4 (review_decision) ruling request; draft minutes.
  • Forbidden outputs: binding ownership into governance_registry; enactment; approval; PG mutation.
  • Expected docs: OP-B packet doc in this package.
  • PASS: owner-per-scope presented with risk + alternatives; C-4 framed; draft minutes ready for council. Unblocks T5 and T10 once council+sovereign (H-2) rule.

T3 — SB-1 governance APR action-type technical design

  • Prerequisite: T0; concept GO.
  • Allowed outputs: uncommitted design of 4 action-types + handler/council-review wiring + interim exception store (admin_fallback_log); rollback drafts; read-only rehearsal log; apply-readiness gate.
  • Forbidden outputs: committed DDL/DML; registering the action-types live; enactment; approval.
  • Expected docs: detailed design under/adjacent to scaffold 05.
  • PASS: 4 action-types fully specified; additive; council-review routing defined; rehearsal green; gate to apply stated.

T4 — SB-2 object/axis ownership-edge technical design

  • Prerequisite: T0; concept GO.
  • Allowed outputs: uncommitted design of additive governance_object_ownership table; proof of no migration risk to the 8 live agency→law edges; rollback; rehearsal log.
  • Forbidden outputs: committed DDL; widening the live CHECK; mutation.
  • Expected docs: detailed design under/adjacent to scaffold 06.
  • PASS: additive table specified; no-migration-risk proven; container-grain inheritance (never per-row at 10^8 scale) addressed; rehearsal green.

T5 — SB-3 generic IU axis-substrate technical design

  • Prerequisite: T2 (OP-B decided) + concept GO.
  • Allowed outputs: Axis Registry as ground truth; generic iu_axis_value store; demote iu_three_axis_envelope to hot-cache projection; prove 4th axis = data not DDL; rollback; rehearsal.
  • Forbidden outputs: committed DDL; ALTERing the live envelope; mutation.
  • Expected docs: detailed design under/adjacent to scaffold 07.
  • PASS: generic store specified; 4th-axis-as-data demonstrated; envelope reframed; OP-B precondition honored.

T6 — Governance-coverage scanner / DOT technical design

  • Prerequisite: concept GO + T3 + T4 accepted.
  • Allowed outputs: 6-layer coverage detector design; scan/propose/apply/audit DOT family (reuse Đ19 orphan scanner + Đ35 DOT pattern + GOV-SIV); dot_coverage_required rows (governance.coverage/classification/pivot/axis/iu) for SB-8; anti-spam path (coalesce_key/cooldown/summary/emit-ceiling) vs live template_gap=182,378; inventory-completeness reconciliation (governance twin of birth-orphan); audit-loop activation (SB-7).
  • Forbidden outputs: committed DOT; production scan emit; event emit; mutation.
  • Expected docs: detailed design under/adjacent to scaffold 08.
  • PASS: detector + DOT family + anti-spam + reconciliation designed; reuse (not island) proven; no emit.

T7 — Issue / event / notification technical design

  • Prerequisite: T0 (informed by T6 for coverage events).
  • Allowed outputs: register-before-emit design under a GOV-SIV governance/integrity event domain; reuse of thiếu_quan_hệ/sai_lệch_dữ_liệu (orphan/drift) and system_issues/event_outbox; Đ45 contract; coalesce/idempotency.
  • Forbidden outputs: event-type registration live; emit; mutation.
  • Expected docs: detailed design under/adjacent to scaffold 09.
  • PASS: event/issue taxonomy designed as register-before-emit reuse; anti-spam honored; no emit.

T8 — Directus / API / render-ownership technical design

  • Prerequisite: C-5 framed (render owner) — default delegation-now/TTL.
  • Allowed outputs: render-shell ownership design (Đ28); API/Directus surface contract for governance reads; reuse of existing Nitro/Directus patterns; no-hardcode acceptance design.
  • Forbidden outputs: route/UI/API/Directus change; new endpoints live; mutation.
  • Expected docs: detailed design under/adjacent to scaffold 10.
  • PASS: render/API ownership designed against Đ28 hub; C-5 default carried; reuse proven; no surface change.

T9 — Registries-Pivot integration technical design

  • Prerequisite: T0; reads patched Registries-Pivot docs (00/04/06/07/08/12) + concept canon.
  • Allowed outputs: design binding the Registries-Pivot surface to the governance concepts (count>1 dual-sense without leaking obligations onto the UI sense; grouping-as-governed-axis; orphan/island dual-channel; pin scope→Class-0); reuse of shipped views/endpoints.
  • Forbidden outputs: UI/API/route/view change; mutation.
  • Expected docs: detailed design under/adjacent to scaffold 11.
  • PASS: integration designed without a second governance roof; M-DEF-10 dual-sense preserved; reuse of live surface; no surface change.

T10 — IU integration technical design

  • Prerequisite: OP-B decided (T2) + SB-3 designed (T5).
  • Allowed outputs: design binding IU (first-class governed object) to coverage/owner/axis under the decided owner-per-scope and generic axis store; non-exemptable reconstruction/vector invariants.
  • Forbidden outputs: IU owner-binding live; axis-envelope ALTER; mutation.
  • Expected docs: detailed design under/adjacent to scaffold 12.
  • PASS: IU integration designed on decided owner + generic axis; invariants preserved; preconditions honored.

T11 — Production implementation (build) — GATED

  • Prerequisite: all upstream gates approved (doc 03 §3.5): SB-1/2/3 resolved; OP-B (C-3)+C-4 ruled; C-5 ruled; L-1/L-2 done; SB-5/6+H-1 enactment phase complete; sovereign sign-off (H-2/SB-6) obtained through the proper path.
  • Allowed outputs: only after the above — committed DDL/DML, DOT registration, scanner, event-type registration, render/API/Directus binding, enactment — each through its ratified, approved channel.
  • Forbidden outputs (until gated): everything in doc 00 §0.6.
  • Expected docs: an implementation-readiness gate doc + per-component build records, in this package.
  • PASS: every gate cleared with a recorded council/human ruling (never self-approval); five-layer sync maintained; no-hardcode; no local island.
Back to Knowledge Hub knowledge/dev/reports/architecture/one-roof-governance-technical-addendum-and-implementation-index-2026-06-01/04-implementation-track-map.md