00 — One-Roof Governance Concept Canon — Index & Control

Path: knowledge/dev/design/one-roof-governance-concepts/00-concept-canon-index.md Status: CONCEPT-LEVEL · DRAFT · NOT enacted · NOT ratified · technical implementation DEFERRED · zero substrate mutation Tier: Concept / principle canonical design only. This canon defines definitions and contracts; it does not design PG schema, DOTs, scanners, apply/remediation binding, IU surface/owner-binding, UI, routes, or APIs. Date: 2026-06-01 Provenance: This is the Round 4 One-Roof Governance Concept Patch. It transcribes the hardened legal/design layer from the controlling Round-4 package into the canonical design home, at the concept tier authorized by that package's CONDITIONAL GO.

---

0.1 Why this canon exists

The One-Roof Governance work to date lived only in report packages under knowledge/dev/reports/architecture/… (Decision Pack → Clause Review → Hardening Revision → Round-4 Finalization). There was no canonical knowledge/dev/design/ home for the governance concepts — only surface designs (Registries-Pivot OS Agency) and the IU/4-Mothers foundation, each of which consumes governance but does not define it.

This canon fills that gap at the concept tier only. It is the shared vocabulary the whole system reconciles against. Surface and foundation designs reference this canon rather than restating it (anti-bloat, mirroring the Điều 37 hub model in doc 02).

0.2 Controlling input (state recovery)

Source	Role
…/one-roof-governance-law-hardening-finalization-round4-2026-06-01/ (14 docs, 00–13)	Controlling. PASS + CONDITIONAL GO for this concept patch. Carries M-DEF-1..10, §0-GOV, the count>1 rule, the Điều 37 centralization decision, the substrate-blocker list, Red-Team v3.
…/gpt-review-round4-one-roof-governance-ready-for-concept-design-patch-2026-06-01.md	External reviewer: "sufficient to move to concept/principle-level canonical design patching … not sufficient for technical PG/DOT/UI implementation, law enactment, remediation binding, or IU surface binding."
…/one-roof-governance-hardening-revision-all-domains-all-axes-2026-06-01/ (17 docs)	Round-3 source of M-DEF-1..9, Open-Axis model, IU first-class, Điều 37 hub.
…/one-roof-governance-clause-review-hardening-2026-06-01/ (17 docs)	Round-2 adversarial clause hardening.
…/one-roof-governance-decision-pack-2026-06-01/ (14 docs)	Round-1 governed-object contract + coverage taxonomy.
knowledge/dev/laws/prompt-muc-tieu-mo-for-claude-code.md	House standard: no_hardcode_absolute, discover_first_reuse_first, five-layer sync, Design-Only Macro Mode.

Round 4 is the latest controlling input. This canon is a true continuation of it, not a restart.

0.3 What Round 4 authorized vs forbade (the scope envelope of this canon)

GO — patch now (this canon's scope): concept/principle canonical design docs carrying M-DEF-1..10 + §0-GOV + the Điều 37 hub OWN/REFERENCE lists + the specialized-law reference pattern, each flagging its blockers.

NO-GO (explicitly excluded from this canon):

• Apply / remediation-binding design (the DOT that writes owner edges) — held behind SB-1, SB-2, SB-3.
• IU owner assignment / IU surface / IU axis-envelope generalization — held behind OP-B, SB-3.
• Any law-file edit, enactment, version bump, approval, or registration — held behind L-1/L-2, H-1, SB-5/SB-6.
• Any PG / Directus / Qdrant / Nuxt / route / API / schema mutation.

This canon carries every "no fixed axis array" claim WITH the SB-3 caveat (the live IU substrate hardcodes 3 axes today — concept-true, substrate-false until generalized).

0.4 Package map

Doc	Content
00	This index + control + scope envelope + concept inventory + blocker summary
01	Governed-object & coverage concepts: One-Roof principle, governed-object contract (M-DEF-1/2 + 13 classes + Class 0), count>1 rule (M-DEF-10), governance-orphan/anarchic (M-DEF-4/5 + 12 gap types), local-governance-island, accountable owner + responsibility scopes (M-DEF-3), governed exception (M-DEF-6), governance grain + coverage invariant v3 + non-hiding inheritance (M-DEF-7), detection obligation + anti-spam, readiness gate, §0-GOV hook
02	Open-axis & IU & Điều 37-hub concepts: open-axis model + Axis Registry (M-DEF-8/9), IU first-class governed domain (concept only; OP-B/SB-3 held), Điều 37 hub OWN/REFERENCE/SPECIALIZE lists, specialized-law reference pattern
03	Blockers carried forward & readiness: SB-1/2/3, OP-B, C-4/5/6, L-1/2, H-1/2, SB-4..9; concept-tier GO vs apply/IU-surface/law/enactment NO-GO; deferred-technical declaration

0.5 Concept inventory — the 18 items this canon carries (mission §3)

#	Concept	Carried in	Clause card	Blocker flag
1	One-Roof Governance principle	01 §1	CLAUSE One-Roof	—
2	Governed Object Contract	01 §2	M-DEF-1, M-DEF-2	—
3	Governance-orphan / anarchic object	01 §4	M-DEF-4, M-DEF-5	—
4	Local-governance-island	01 §5	CLAUSE Island	—
5	Open-axis model	02 §1	M-DEF-8	SB-3
6	Axis Registry concept	02 §2	M-DEF-9	SB-2, SB-3
7	IU as first-class governed domain (concept only)	02 §3	CLAUSE IU first-class	OP-B, SB-3
8	count > 1 as candidacy trigger, not mandate	01 §3	M-DEF-10	—
9	Container-grain inheritance / non-hiding rule	01 §8	M-DEF-7	—
10	Accountable owner vs supporting roles	01 §6	M-DEF-3	—
11	Governed exception model	01 §7	M-DEF-6	SB-1 (native store)
12	Governance Coverage Invariant v3	01 §8	CLAUSE Invariant v3	SB-3 (IU/axis grain)
13	Law-level detection obligations	01 §9	CLAUSE Detection	SB-8
14	Noise / scale control (anti-spam)	01 §10	CLAUSE Anti-spam	—
15	Điều 37 hub model / §0-GOV hook	01 §11, 02 §4	CLAUSE §0-GOV	L-2 (Đ20 reg)
16	Specialized-law reference pattern	02 §5	PATTERN ref	doc 07 deps
17	Readiness gate concept	01 §12	CLAUSE Readiness gate	—
18	Explicit blocker / prerequisite flags	03	—	all

0.6 Blocker summary (full register in doc 03)

ID	Blocker	Class	Holds
SB-1	Missing governance APR action-types (assign_governance_owner / grant_governance_exception / delegate_authority / assign_axis_owner)	substrate + council (C-2)	apply (PROPOSE)
SB-2	Object/axis ownership edge un-expressible (governance_relations CHECK ∈ {law,agency})	substrate + council (C-1)	apply (APPLY)
SB-3	IU iu_three_axis_envelope hardcodes exactly 3 axes in DDL	substrate	open-axis at IU substrate
OP-B	IU family accountable owner unassigned (no GOV-IU agency; owner_ref free-text on all 219 IUs)	council (C-3) + human (H-2)	IU surface / owner-binding
C-4	review_decision as approval adapter vs full Đ32 routing	council	IU approval routing
C-5	GOV-MOUT / display-render owner unresolved (Đ28 agency-orphaned)	council	render-binding
L-1 / L-2	Enacted-law drift (Đ36/37/45) + register Đ20/23/44/45 in normative_registry	law-drift	law-file patch
H-1 / SB-5 / SB-6	Enact handlers unimplemented; os_proposal_approvals=0; no sovereign sign-off	human	enactment

Net council/human decision surface = 8 (C-1..C-6, H-1, H-2), each with a recommended default in the Round-4 ledger (doc 02 of the Round-4 package). None of these blocks the concept tier; every one of them blocks a later tier.

0.7 Reading contract for downstream designers

1. Treat every M-DEF and CLAUSE card as a contract the system reconciles against, not as an implementation spec.
2. Where a card carries a blocker flag, do not design the blocked tier here — flag it and defer.
3. Surface/foundation designs reference these cards by ID (e.g. "per One-Roof Concept Canon M-DEF-10"); they must not re-define them (Điều 37 anti-bloat).
4. Nothing in this canon may be cited as enacted law or as a ratified decision. It is a concept proposal awaiting the council/human surface in doc 03.