01 — Current State & Controlling Sources

Read after doc 00. This doc states what is now accepted and lists the controlling sources in priority order. For the full current/reference/superseded classification of every doc, see doc 02.

---

1.1 What is now accepted (the settled state)

Layer	State	Where it lives
Governance concept layer	ACCEPTED at concept tier (PASS / CONDITIONAL GO). Definitions M-DEF-1..10, §0-GOV hook, count>1 rule, open-axis model, IU-first-class concept, coverage invariant v3, Điều 37 hub, governed-exception, anti-spam, 4-phase readiness gate.	knowledge/dev/design/one-roof-governance-concepts/ (00–03) — the canonical concept home
Law/clause layer	DRAFT, hardened, NOT enacted. Consolidated hardened clause text; open-question ledger closed; all-domain proof; Red-Team v3 100% caught.	…/one-roof-governance-law-hardening-finalization-round4-2026-06-01/ (esp. doc 10 consolidated clauses)
Surface design (Registries-Pivot)	Concept-patched (docs 00/04/06/07/08/12 reference the canon). Shipped surface is live; governance binding is not built.	knowledge/dev/design/registries-pivot-os-agency/
IU foundation	IU recognized as a first-class governed object (concept). IU owner-binding, approval routing, and axis-envelope generalization are DEFERRED (OP-B, C-4, SB-3).	knowledge/dev/design/iu-mow-mot-event-foundation-design.md
Substrate (live PG)	Unchanged. Governance APR action-types, object/axis ownership edge, generic IU axis store, coverage scanner/DOTs, governance event types — all absent. These are the blockers.	live directus DB (read-only evidence in Round-4 doc 08)
Technical implementation	NONE approved, NONE built.	—

Net: concept is done; everything from substrate design onward is gated. See doc 03 for the gates.

1.2 Controlling sources — priority order

Listed highest-authority first. When two disagree, the higher entry wins (consistent with doc 00 §0.2).

S0 — House operating constitution (above everything)

• Path: knowledge/dev/laws/prompt-muc-tieu-mo-for-claude-code.md (Chuẩn 100000x, rev 41)
• Controls: how any macro runs — no-hardcode absolute, discover-first/reuse-first, five-layer sync, Design-Only Macro Mode, live-apply hard gate, Điều 45 queue law.
• Does not control: the governance domain content itself.
• Read requirement: MANDATORY for every macro. Never overridden by anything in this package.

S1 — This implementation index (the entrypoint)

• Path: …/one-roof-governance-technical-addendum-and-implementation-index-2026-06-01/ (this package)
• Controls: where work starts, what is allowed/forbidden, conflict resolution, where docs are written.
• Does not control: concept definitions (it points to them) or law wording (it points to it).
• Read requirement: MANDATORY first (doc 00).

S2 — Concept canon (current concept truth)

• Path: knowledge/dev/design/one-roof-governance-concepts/ (00 index, 01 governed-object & coverage, 02 open-axis/IU/Điều37-hub, 03 blockers & readiness)
• Controls: all governance definitions and contracts the system reconciles against (M-DEF-1..10, §0-GOV, count>1, open-axis, IU-first-class concept, invariant v3, Điều 37 hub).
• Does not control: PG schema, DOTs, scanners, apply/remediation binding, IU surface/owner-binding, UI, routes, APIs (all explicitly deferred there).
• Read requirement: MANDATORY for any track that touches a definition. Treat as read-only reference from implementation tracks; changing it is a concept-patch macro, not implementation.

S3 — Round-4 law hardening finalization (current law/clause draft truth)

• Path: …/one-roof-governance-law-hardening-finalization-round4-2026-06-01/ (00–13; esp. 02 open-question closure, 08 live-PG compatibility, 10 consolidated hardened clauses, 11 GO/NO-GO, 12 next prompts)
• Controls: hardened clause wording (DRAFT), the closed open-question ledger, the blocker definitions, the live-substrate evidence snapshot, the GO/NO-GO boundary.
• Does not control: enactment (the clauses are DRAFT, not in normative_registry); concept-home placement (that is S2).
• Read requirement: MANDATORY for law-cleanup (T1) and for any track citing clause wording. Wins over Round 1/2/3 wording.

S4 — Round-4 concept-patch report + GPT external review (provenance + concurrence)

• Paths: …/patch-canonical-design-one-roof-concepts-round4-2026-06-01/ (00–08) and …/gpt-review-round4-one-roof-governance-ready-for-concept-design-patch-2026-06-01.md
• Controls: the record of how the concept canon (S2) was produced and why the concept tier is GO; the external reviewer's confirmation that concept patching is OK but technical/enactment/IU-surface/remediation are NOT.
• Does not control: it is a report about S2, not a substitute for S2. If the report and the canon ever diverge, the canon (S2) is the live artifact.
• Read requirement: Recommended for provenance; MANDATORY input to the external-critique prompt (doc 14 #1).

S5 — Patched Registries-Pivot surface design (current surface, mixed tiers)

• Path: knowledge/dev/design/registries-pivot-os-agency/ — patched docs 00, 04, 06, 07, 08, 12 carry the concept-canon references.
• Controls: how the Registries-Pivot surface consumes governance (count>1 drill, grouping-as-governed-axis, orphan/island channel, pin scope, readiness gate).
• Does not control: governance definitions (those are S2); and the un-patched technical content here is reference-only (see doc 02). The shipped route/API/views are live substrate, not a governance-binding spec.
• Read requirement: MANDATORY for the Registries-Pivot integration track (T9). Read the patched docs as current; treat older revisions as reference.

S6 — Patched IU foundation design (IU concept first-class; IU technical deferred)

• Path: knowledge/dev/design/iu-mow-mot-event-foundation-design.md
• Controls: IU as a first-class governed object concept (IU-GOV-1..5 references).
• Does not control: IU owner assignment (OP-B), review_decision approval routing (C-4), and the IU axis-envelope generalization (SB-3) — these are HELD/DEFERRED and must not be read as designed.
• Read requirement: MANDATORY for IU integration (T10) and OP-B packet (T2); read only the IU-first-class concept as current.

1.3 Read-requirement summary by track

Track	Must read (beyond S0+S1)
T1 law cleanup	S3 (doc 07 patch matrix, doc 08 drift), enacted law files (as drift evidence only)
T2 OP-B packet	S2 doc 02, S3 doc 05, S6
T3 SB-1 / T4 SB-2	S2 doc 03, S3 doc 02 + 08
T5 SB-3	S2 doc 02+03, S3 doc 05, S6, after T2
T6 scanner	S2 doc 01, S3 doc 08, S5 doc 06/09, after T3+T4
T7 issue/event	S3 doc 08 (SB-4), S5 doc 09
T8 render/API	S5 doc 10, S2 doc 02 (Điều 37 hub C-5)
T9 Registries-Pivot	S5 (patched docs), S2
T10 IU integration	S6, S2 doc 02, after OP-B + SB-3