KB-5E62
04 — All-Laws Reconciliation: Keep / Centralize / Reference / Patch / Defer (Branch D) (2026-06-01)
10 min read Revision 1
one-roof-governancehardening-revisionbranch-dlaw-reconciliationkeep-centralize-reference-patch-deferdieu37-hubconstitutiondieu44dieu31dieu32dieu352026-06-01
04 — All-Laws Reconciliation: Keep / Centralize / Reference / Patch / Defer (Branch D)
Reconciles One-Roof Governance with every relevant law. For each: what it governs, what governance-related content exists, and a verdict in five categories — KEEP (stays in the law as-is), CENTRALIZE (conceptually owned by Điều 37, the law references it), REFERENCE (the law adds a cross-ref to Điều 37), PATCH (clause text revision proposed in doc 13, draft-only), DEFER (needs council/substrate before touching). Goal: make Điều 37 the hub without bloating it (doc 05). All verdicts are DRAFT proposals; no enactment, no version bump.
4.1 Reconciliation principle
The governance model (what is a governed object, what is anarchic, the coverage invariant, ownership scopes, the open-axis model, the exception model, the readiness gate) is single-source-of-truth in Điều 37. Specialized laws declare governance hooks that reference Đ37 and add domain-specific detail; they do not redefine the model. A specialized law that re-states or contradicts the model is a doc-drift defect (doc 14 OQ-J10). This is the "no local governance island at the law level" rule.
4.2 Keep / Centralize / Reference / Patch / Defer matrix
| Law | Currently governs | Governance content present | Verdict | Folded action |
|---|---|---|---|---|
| Hiến pháp / Constitution | supreme principles incl. NT4 "cấm hardcode", separation of powers | the no-hardcode rule; agency legitimacy | KEEP + REFERENCE | Constitution keeps NT4; Đ37 references NT4 as the root of "no hardcoded axis array" (doc 02 §2.10). One-Roof principle is a Đ37 elaboration of constitutional separation-of-powers, not a new supreme rule |
| Điều 0 / Information Atom | atomic information unit foundation | none governance-specific | KEEP | atoms are governed objects; coverage profile assigned via Đ37, no Đ0 change |
| Điều 0-B / Composition layer | composition levels (atom/molecular/composite) | composition is an axis | REFERENCE | composition axis registered in Axis Registry (doc 02); Đ0-B references Đ37 axis model; no redefinition |
| Species taxonomy (Đ29) | species classification vocab | classification is an axis; species vocab | REFERENCE + PATCH(owner-split) | species axis vocab → GOV-KG-SYS substrate owner, COUNCIL policy owner (M-Đ24/29 §0-OWNER). Đ29 references Đ37 |
| Điều 0-G / Birth Registry | object birth / orphan detection | birth-orphan detection (the model for governance-orphan) | KEEP + REFERENCE (precedence) | birth-orphan stays in Đ0-G; Đ37 declares governance coverage is a layer above birth (M-DEF-4 precedence). Đ0-G references the dedup rule |
| Điều 2 / Registry | registry objects, registry pattern | registries are governed objects; pivot/pin/axis registries reuse this | KEEP + REFERENCE | Axis Registry (M-DEF-9), route inventory, threshold-policy table all reuse Đ2 pattern; Đ2 references Đ37 coverage profiles |
| Điều 20 / Design-before-implementation | no impl before ratified design | the readiness gate lives near here | REFERENCE + PATCH | Đ37 §4.18 readiness gate (tiered, severity-aware) references Đ20's design-gate; Đ20 references Đ37 governance-coverage gate as a precondition to its impl gate |
| Điều 23 / DOT scanning | scan operations | scanners are governed DOTs | REFERENCE | coverage scanner is a governed DOT under Đ35/Đ31; Đ23 references Đ37 (scanner is itself a governed object, anti-bootstrap) |
| Điều 24 / Label-Taxonomy | facets, label_rules, grouping | grouping ceiling, pin policy, classification — heavy governance content; agency-orphaned | PATCH(owner-split) + REFERENCE | M-Đ24 §0-OWNER: cross-system policy → COUNCIL; substrate (facets/label_rules/species) → GOV-KG-SYS. max_ungrouped ≤ 50 = COUNCIL-owned threshold row, not literal. Don't centralize substrate on policy owner |
| Điều 26 / Pivot | pivot definitions, pivot_count() |
pivot coverage; PIVOT_MISSING; agency-orphaned | PATCH + REFERENCE | M-Đ26 §0-OWNER: pivot inherits source-collection owner only if source is covered (anti-hiding); else pivot_coverage_unowned. Health edge GOV-SIV→NRM-LAW-26. Đ26 references Đ37 |
| Điều 28 / Display-Nuxt boundary | render boundary, Test-4 (100% Nuxt=PG) | render ownership; agency-orphaned, MOUT draft | PATCH(interim delegation) + REFERENCE | M-Đ28 §0-OWNER: render→GOV-MOUT; pending activation, COUNCIL holds via TTL-bounded delegation (so render objects are covered-by-delegation, gate stays usable). NT-D1-ext: Nitro server/api/** in render tier, no truth-math. Đ28 references Đ37 |
| Điều 30 / Rollback | reversibility, soft-delete | rollback is a risk-required link in coverage profiles | KEEP + REFERENCE | profiles requiring rollback (DOT/EXCEPTION/POLICY) reference Đ30; Đ30 unchanged |
| Điều 31 / Audit-System Integrity | the 5 integrity checks; orphan detection | the detection home — governance coverage is the 6th check | CENTRALIZE-detection + PATCH | M-Đ31 §4.3-Loại6: 6th check = Governance Coverage, cross-ref to Đ37 §4.15 (does NOT redefine). §4.8-ext severity-aware gate; §4.9-ext inventory-completeness + context triggers. Detection mechanism stays in Đ31; the definitions are Đ37's |
| Điều 32 / Approval | APR spine, quorum | approval path — risk-required link | KEEP + PATCH(action-types) + DEFER(substrate) | needs the 4 new action-types (assign_governance_owner/grant_governance_exception/delegate_authority/assign_axis_owner) — substrate prerequisite (T1-6). Đ32 references Đ37 for which changes need approval |
| Điều 35 / DOT Governance | dot_tools SSOT, paired DOTs |
execution authority — risk-required link | PATCH + REFERENCE | M-Đ35 §6.2-bis: coverage-DOT lifecycle DETECT→PROPOSE→APPROVE→APPLY→VERIFY→CLOSE; SoD; bootstrap seed; PROPOSE needs registered action-types (T1-6). IU DOTs must register here (doc 03). Đ35 references Đ37 |
| Điều 36 / Collection | collections/tables as objects | substrate objects are governed | KEEP + REFERENCE | collection coverage profile via Đ37; resolve v4.0/v5.0 status drift (OQ-J10) before any patch |
| Điều 37 / Governance Organization | agencies, ownership, §4.12 one-owner | THE HUB | CENTRALIZE (own the model) | owns: One-Roof principle, governed-object def, anarchic def, coverage invariant, scope/role model, open-axis model, exception model, readiness-gate hook, scanner hook. See doc 05 for own-vs-reference split |
| Điều 39 / KG | knowledge-graph edges | KG/relation axis; "propose-only, never auto-mutate" | REFERENCE | IU KG edges + universal_edges register relation axis (doc 02/03); Đ39 references Đ37; KG-write DOT gap noted |
| Điều 41 / Host-API-deploy | VPS, deploy ledger | Direct-PG exception, deploy ledger (vps_deploy_log) |
PATCH(exception) + REFERENCE | M-Đ28 §VIII-ext + doc 08: Direct-PG read-only adapter = governed exception, verified vs information_schema grants, ledgered in vps_deploy_log, QUARANTINED transitional. Đ41 references Đ37 exception model |
| Điều 44 / IU | object-family schema-logic (DRAFT) | IU is a governed domain (doc 03); axes; family registry | REFERENCE + DEFER(owner OP-B) | Đ44 references Đ37 for IU coverage; IU axes register in Axis Registry; DEFER binding IU owner until OP-B council decision (doc 03 §3.5). When Đ44 enacts, it declares its governance hooks, does not redefine the model |
| Điều 45 / Event-Queue | event_type_registry, register-before-emit |
issue/event path — risk-required link | PATCH(names+vocab) + REFERENCE | M-Đ45 §3.2: register-before-emit for governance events; correct names (live = bare governance.*/proposal.* under mother domain, all active=false); decide new GOV-SIV governance/integrity domain (OQ-H1). Extend to register-before-write issue_type vocabulary. Đ45 references Đ37 |
| Operating Rules | Đ45 register-before-emit, Đ37 SSOT discipline | procedural | KEEP + REFERENCE | OR keeps procedure; references Đ37 for the governance model |
4.3 What must NOT move to Điều 37 (anti-bloat)
To keep Đ37 a hub and not a dumping ground, the following stay in specialized laws and are only referenced:
- Detection mechanics (how to scan, the 6-layer scanner, the queries) → stay in Đ31 (Đ37 declares the obligation, Đ31 owns the method).
- Approval mechanics (quorum math, APR lifecycle states) → stay in Đ32.
- DOT execution mechanics (paired_dot, tier-A/B triggers) → stay in Đ35.
- Vocabulary substrate (facets, label_rules, species, event types) → stay in Đ24/Đ29/Đ45; Đ37 owns only the policy that these need owners and approval.
- Render mechanics (Test-4, Nuxt boundary) → stay in Đ28.
- IU schema/profile detail → stay in Đ38/Đ44; Đ37 owns only the coverage obligation.
The rule: Điều 37 owns definitions and obligations; specialized laws own mechanisms and substrate. (Doc 05 formalizes this split.)
4.4 Drift to resolve before any law patch (content-only, not in this mission)
- Đ45 has a
ban_hanh=falseleftover; Đ36 has v4.0-vs-v5.0 ambiguity (OQ-J10). These are authoritative-status questions for GOV-NRM-SYS (active) to resolve content-only before P3 (doc 15 prompt 6). - Enacted Đ37 v3.3 capability JSON vs live columns drift (prior packages); the governance_docs UI index is stale. Resolve content-only.
Branch-D verdict
All 20+ relevant laws are reconciled into a keep/centralize/reference/patch/defer matrix. The model is centralized in Đ37; specialized laws reference it and keep their mechanisms. Three laws need substrate before patch (Đ32 action-types, Đ37 §5.4-EXT, the Axis Registry under Đ2) — all the same T1-6 prerequisite. The rest are wording PATCH or pure REFERENCE.