Incomex AI Portal
KB-5FB4 rev 2

00 — READ ME FIRST — One-Roof Governance Implementation Index (2026-06-01)

10 min read Revision 2
one-roof-governanceimplementation-indexread-me-firstcontrolling-entrypointblockerstracksconcept-completetechnical-not-approvedno-mutation2026-06-01

00 — READ ME FIRST — One-Roof Governance Implementation Index

Related design addendum (2026-06-02): the axis-proposal & authorization operating-substrate design lives at knowledge/dev/reports/architecture/one-roof-axis-proposal-authorization-operating-substrate-design-2026-06-01/ (docs 00–15). It redefines M-1 (technical build authorization via a new governance_build_authorization record + an L0–L4 ladder; os_proposal_approvals reserved for L4 sovereign e-sign only) and designs the common axis/topic operating model. See that package's doc 13 for the exact patches to fold back here (M-1 redefinition, SB-0 authorization substrate, axis_registry/axis_assignment, fn_auto_approve_add fix).

Path: knowledge/dev/reports/architecture/one-roof-governance-technical-addendum-and-implementation-index-2026-06-01/ Status: Concept patch COMPLETE · Technical implementation NOT YET APPROVED. This package is an implementation-control package, not implementation. Role: This is the active implementation entrypoint for all One-Roof Governance work until a newer explicit implementation index supersedes it. Date: 2026-06-01 · Mutation footprint: KB documents only. Zero PG / Directus / Qdrant / Nuxt / schema / DOT / law / approval mutation.

0.1 THE RULE (mandatory for every future agent)

All future One-Roof Governance implementation work MUST begin from this package.

Do not start from old Round 1/2/3 reports, old Registries-Pivot technical designs, old IU docs, or live PG observations as if they were current implementation truth. Go through this index first. It tells you what controls, what is reference-only, what is blocked, and what you are allowed to design next.

This package stays the entrypoint until superseded by a newer explicit implementation index that names itself as the replacement.

0.2 Conflict-resolution order (when two docs disagree)

  1. This implementation index wins over older reports.
  2. Concept canon (knowledge/dev/design/one-roof-governance-concepts/) wins over pre-patch design text.
  3. Round-4 law hardening (…/one-roof-governance-law-hardening-finalization-round4-2026-06-01/) wins over earlier (Round 1/2/3) wording.
  4. Blockers win over implementation ambition — a named open blocker (doc 03) defeats any plan that needs it resolved.
  5. If still unclear → STOP and report. Do not guess, do not self-approve, do not invent a path.

The house standard knowledge/dev/laws/prompt-muc-tieu-mo-for-claude-code.md (no-hardcode, discover-first/reuse-first, five-layer sync, Design-Only Macro Mode, live-apply hard gate) sits above all of the above as the operating constitution; nothing here overrides it.

0.3 Mandatory read order

# Read Why
1 This doc (00) the rule, the gates, the entrypoint
2 01-current-state-and-controlling-sources.md what is accepted + the priority-ordered controlling source list
3 02-source-map-current-vs-reference-vs-superseded.md which docs are truth, which are reference, which are dead
4 03-blocker-register-and-gates.md the open blockers that gate everything
5 04-implementation-track-map.md the allowed tracks T0–T11 and their prerequisites
6 the scaffold for your track (05–12) scope, constraints, acceptance for the design you are about to write
7 13-implementation-handoff-short.md the one-screen recap (also good to paste into a prompt)

Then — and only then — read the controlling design/law sources named in doc 01 for your specific track.

0.4 Current status in one paragraph

The One-Roof Governance concept layer is complete and tight: hardened definitions M-DEF-1..10, the §0-GOV hook, the count>1 relevance rule, the open-axis model, IU-as-first-class concept, coverage invariant v3, the Điều 37 hub model — all transcribed into the canonical concept home knowledge/dev/design/one-roof-governance-concepts/ (00–03) and reflected into the patched surface/foundation designs. The Round-4 finalization closed the open-question ledger (zero unclassified), proved all-domain coverage, and passed Red-Team v3 at 100% caught. Verdict: PASS / CONDITIONAL GO. What remains is not concept work — it is substrate, council/human decisions, law-drift cleanup, and enactment, each a named, detected, upgrade-pathed blocker. No technical design has been approved or built.

0.5 Allowed tracks (design-only unless a gate is met — see doc 04)

  • T0 — this index/control package (current).
  • T1 — content-only law cleanup / registration-drift design (DRAFT packet only; L-1/L-2).
  • T2 — OP-B IU-owner decision packet (council minutes draft; no binding).
  • T3 — SB-1 governance APR action-type technical design (uncommitted DDL/rehearsal).
  • T4 — SB-2 object/axis ownership-edge technical design (additive table; uncommitted).
  • T5 — SB-3 generic IU axis-substrate technical design (gated on OP-B / T2).
  • T6 — governance-coverage scanner/DOT technical design (gated on T3+T4 + concept GO).
  • T7 — issue/event/notification technical design.
  • T8 — Directus/API/render-ownership technical design (gated on C-5).
  • T9 — Registries-Pivot integration technical design.
  • T10 — IU integration technical design (gated on OP-B + SB-3).
  • T11 — production implementation — only after all upstream gates are approved.

Every track T1–T10 produces design documents inside this package, plus at most read-only / BEGIN..ROLLBACK rehearsal. None commits anything.

0.6 Forbidden until the relevant blocker is resolved (hard list)

  • ❌ PG mutation (committed DDL/DML); ❌ Directus mutation; ❌ Qdrant/vector write; ❌ Nuxt/UI/API/route change.
  • ❌ Schema/table/view/function creation; ❌ DOT registration or implementation; ❌ event/job/notification emit.
  • ❌ Law enactment; ❌ version bump; ❌ status change; ❌ write to normative_registry / law_catalog / governance_docs.
  • ❌ Approval creation; ❌ self-approval.
  • ❌ "Technical implementation disguised as scaffold"; ❌ implementing from a stale doc; ❌ hardcode; ❌ a hidden local governance island (a second governance roof).

0.7 Where to write new docs

All future One-Roof Governance technical docs go inside THIS package (…/one-roof-governance-technical-addendum-and-implementation-index-2026-06-01/) unless a later prompt explicitly moves them. Use the scaffold docs (05–12) as the home for each track's detailed design; if a track needs more than one doc, number it under the same package (e.g. 06a-…, 06b-…) and add a pointer line to the relevant scaffold. Do not scatter One-Roof Governance docs into unrelated design folders. The concept canon (knowledge/dev/design/one-roof-governance-concepts/) is read-only reference from here — do not edit it as part of implementation; if a concept must change, that is a concept-patch macro, not an implementation track.

0.8 What counts as STALE input (do not implement from these)

  • Round 1 Decision Pack, Round 2 Clause Review, Round 3 Hardening Revision — superseded for wording by Round 4.
  • Pre-patch Registries-Pivot technical designs and the Registries-Pivot ship/macro reports — technical/historical reference only; they describe live substrate, not governance-concept truth.
  • The IU foundation doc's technical IU sections (owner-binding, 3-axis envelope) — deferred, pending OP-B and SB-3.
  • Any enacted law file text that conflicts with Round-4 wording — that conflict is blocker L-1 (drift), not a license to follow the stale text.
  • Live PG state read in isolation — evidence, not a mandate; reconcile against the concept canon and blockers.

0.9 Minimum final-report fields for every future agent

Any agent finishing a One-Roof Governance track under this package must return:

  1. Status — PASS / PARTIAL (+exact blocker) / BLOCKED.
  2. Track — which T# (doc 04) and which scaffold doc it advanced.
  3. Controlling sources used — exact paths, with the doc-01 priority order honored.
  4. Blockers touched — which of doc 03 it advanced, and which remain open (none silently closed).
  5. Mutation footprint — explicit: KB-only / read-only PG / rehearsal-only; confirm zero committed PG/Directus/Qdrant/Nuxt/law/approval mutation.
  6. Where it wrote — paths inside this package.
  7. Gate check — which gate it cleared, which gate(s) still block the next tier.
  8. No-hardcode / no-local-island attestation.
  9. Next allowed macro — the next prompt from doc 14.

0.10 Copy-paste preamble for future One-Roof Governance prompts

STATE RECOVERY (mandatory): Read, in order:
  1. knowledge/dev/reports/architecture/one-roof-governance-technical-addendum-and-implementation-index-2026-06-01/00-read-me-first-implementation-index.md
  2. …/01-current-state-and-controlling-sources.md
  3. …/02-source-map-current-vs-reference-vs-superseded.md
  4. …/03-blocker-register-and-gates.md
  5. …/04-implementation-track-map.md
  6. the scaffold doc for this track (05–12)
This index controls. Concept canon > pre-patch design. Round-4 law > earlier wording.
Blockers win over ambition. If unclear, STOP and report.
HARD GATE 0: no PG/Directus/Qdrant/Nuxt mutation; no schema/DOT/UI/API; no enactment/
  version-bump/status-change/registry-write; no approval/self-approval; no hardcode;
  no hidden local governance island; no implementation disguised as scaffold.
Write all new docs inside this package. Return the doc-00 §0.9 minimum final-report fields.
Back to Knowledge Hub knowledge/dev/reports/architecture/one-roof-governance-technical-addendum-and-implementation-index-2026-06-01/00-read-me-first-implementation-index.md