07 — Specialized-Law → Điều 37 Patch Matrix (Branch G)

For each law family, the exact patch relationship to Điều 37. No law file is patched here — this is the matrix that a later content-only law-patch macro (doc 12 prompt 4) will execute, after the substrate/council blockers clear.

Patch-type vocabulary: REF (add a reference clause to Đ37) · NEW (new clause) · CONTENT (content-only correction) · CLEANUP (drift fix) · REGISTER (add the law to normative_registry) · NONE.

Live enactment status (re-verified, normative_registry 47 rows): enacted = Đ0-G, Đ2, Đ24, Đ26, Đ28, Đ30, Đ31, Đ32(V1P1), Đ35(V5P2), Đ36, Đ37(v3.3), Đ38, Đ39, Đ41, Đ43, HP(v4.6.3); draft = Đ34; absent (KB-only) = Đ20, Đ23, Đ44(draft), Đ45.

---

7.1 Patch matrix

Law	Current role	Governance gap	Patch?	Type	Proposed wording (summary)	Blocker / dependency	Acceptance criterion
Đ0-G Birth Registry	Enacted; orphan scanner (Đ19) live; births objects	None major — birth precedes governance	Yes	REF	"Governance coverage is a layer above birth; an unborn object raises a birth-orphan, not an OWNER_GAP (M-DEF-4 precedence)."	none	Unregistered object → 1 birth issue, 0 governance issue.
Đ2 Registry	Enacted; "everything has an ID + a managing list"	Axis/Object registries must follow Đ2 pattern	Yes	REF	"The Axis Registry and governance_object_ownership are Đ2 registries; born via Đ0-G, owned per Đ37."	SB-2 (object table)	Axis Registry absent → inventory_gap.
Đ20 Design-before-Implementation	KB-only, unregistered	Not in normative_registry; the §0-GOV hook lives at the Đ20 review gate	Yes	REGISTER + NEW	Register Đ20; add "§0-GOV hook required at design review; absence = governance_hook_missing."	L-2 (register)	New doc without §0-GOV → blocked at review.
Đ23 DOT Scanning	KB-only, unregistered	Detection mechanism for the coverage scanner	Yes	REGISTER + REF	Register Đ23; "coverage scanner reuses the Đ23 scan pattern under GOV-DOT."	L-2	Coverage scan path = a registered Đ23 scan.
Đ24 Label/Taxonomy	Enacted; classification domain primary	Agency-orphaned (no agency owns classification); label dim = an axis	Yes	REF + CONTENT	"Label dimensions are axes (Axis Registry); classification domain owned by GOV-KG-SYS (OQ-J7)."	C/OQ-J7 (owner)	classification domain has an owner edge.
Đ26 Pivot	Enacted; pivot domain primary	Agency-orphaned; pivot group-by = an axis; grouping ceiling policy un-homed	Yes	REF + NEW	"Pivot group-by is an axis; grouping policy (ceiling ≤50/pin/threshold) is an Axis-Registry attribute owned per Đ37."	owner assignment	New group-by unregistered → axis_unregistered.
Đ28 Display/Nuxt	Enacted; render boundary	Agency-orphaned; 0 enforcing DOTs; no display/render domain; GOV-MOUT born of Đ7 not Đ28	Yes	REF + CLEANUP	"Render/display owned by GOV-MOUT (after activation + Đ28 binding, C-5); display truth math forbidden in Nuxt."	C-5 (MOUT activation)	A render surface has a live owner.
Đ30 Rollback/Regression	Enacted	Rollback is a profile-mandatory link for mutating objects	Yes	REF	"Mutating governed objects require a Đ30 rollback link; read-only surfaces exempt (OQ-B2)."	none	Mutating object no rollback → ROLLBACK_GAP.
Đ31 System Integrity	Enacted; owned by GOV-SIV; 22 DOTs (most-equipped)	The coverage detector + invariant live here	Yes	NEW	"GOV-SIV computes the coverage accounting identity + governance-orphan/anarchy detection (twin of birth-orphan); new governance/integrity event domain (OQ-H1)."	L-2 (Đ45 reg), event domain	Coverage identity computed + closes per scope.
Đ32 Approval	Enacted (V1P1); the spine	Missing governance action-types	Yes	REF + NEW	"Authority-bearing governed actions pass Đ32 via assign_governance_owner/grant_governance_exception/delegate_authority/assign_axis_owner (C-2)."	SB-1 / C-2 (substrate)	Mutating object no APR → APPROVAL_PATH_GAP.
Đ35 DOT Governance	Enacted (V5P2); owned by GOV-DOT	Coverage DOT family + IU command catalog must register here	Yes	REF + NEW	"Coverage scan/propose/apply/audit DOTs + IU 54-command catalog register into dot_tools with paired_dot; no parallel DOT catalog."	IU design (catalog bind)	IU command not in dot_tools → DOT_AUTHORITY_GAP.
Đ36 Collection	Enacted; v4.0 (index) vs v5.0 (file draft)	Drift (version ambiguity)	Yes	CLEANUP	Resolve authoritative version (content-only, NRM-SYS).	L-1 (J10)	Single authoritative Đ36 version.
Đ37 Governance Org	Enacted v3.3; hub	Enacted text vs live columns drift; needs all OWN clauses (doc 06)	Yes	NEW + CLEANUP	Add §4.15..§4.18 + §0-GOV (doc 06); reconcile v3.3 text to live gov_type/created_by_law/relation_type/enforcement_role+capability.	L-1 (drift)	Enacted Đ37 text = live columns; OWN clauses present.
Đ41 Host/API/VPS	Enacted	Agency-orphaned; hosts the un-ledgered Direct-PG adapter	Yes	REF + NEW	"Host/deploy owned (GOV-SIV/Đ41); read-only Direct-PG adapter ratified as a governed exception OR replaced by PK-views via Directus; back-fill vps_deploy_log."	council (Direct-PG)	Direct-PG path has an exception record or is retired.
Đ44 IU (UOSL)	DRAFT v0.1.2, unregistered	IU family owner unassigned (OP-B); IU island	Yes	REGISTER(draft) + REF	Register Đ44 as draft; "IU is a first-class governed domain under Đ38; owner per OP-B; axes via Axis Registry (no fixed IU axis list)."	OP-B (C-3) + L-2	IU object has an owner edge; IU axes registered.
Đ45 Event/Queue	KB-enacted (v1.0) but unregistered; ban_hanh=false leftover	Not in normative_registry; register-before-emit gate; governance event domain needed	Yes	REGISTER + CLEANUP + NEW	Register Đ45; strip ban_hanh=false leftover (CLEANUP); "new governance/integrity/coverage/axis event domains register before emit (OQ-H1)."	L-1 + L-2	Đ45 in registry; governance events registered, not bare mother.*.
Đ38 NRM / Đ39 KG / Đ0-B / Đ34	Enacted (Đ34 draft)	Đ34 (Workflow) draft — workflows owned by GOV-MOW (draft)	Partial	REF	"Workflows are governed objects (DOT/POLICY) owned by GOV-MOW; reference Đ37 coverage."	Đ34 enactment, GOV-MOW activation	Workflow design has owner + coverage.

---

7.2 Patch-type rollup

• REGISTER (law-registration gap, L-2): Đ20, Đ23, Đ44(draft), Đ45 — must be added to normative_registry before any clause referencing them is patched into law.
• NEW clauses: Đ37 (the OWN clauses), Đ31 (detector+invariant), Đ32 (action-types), Đ35 (coverage DOT family), Đ41 (Direct-PG exception), Đ45 (governance event domains).
• REF clauses (point to Đ37): Đ0-G, Đ2, Đ24, Đ26, Đ28, Đ30, Đ34, Đ44.
• CLEANUP (drift, L-1): Đ36 (version), Đ37 (text vs columns), Đ45 (ban_hanh=false).
• NONE: the operational laws (Đ1, Đ3–Đ19, Đ22) — unaffected by the governance-coverage layer.

---

7.3 Dependency sequencing (what blocks what)

1. Content-only prerequisites (no substrate): L-1 drift fixes (Đ36/Đ37/Đ45) + L-2 registrations (Đ20/23/44/45). These are GOV-NRM-SYS content work, independent of substrate. They block a clean law patch, not the design patch.
2. Substrate prerequisites: SB-1 (Đ32 action-types) + SB-2 (Đ37/Đ31 object edge) + SB-3 (Đ44 axis envelope). Block apply/remediation clauses.
3. Council prerequisites: OP-B (Đ44 owner), OQ-J7 (Đ24 owner), C-5 (Đ28/MOUT), Direct-PG (Đ41). Block owner-binding clauses.

The concept-level Đ37 hub clauses (doc 06 OWN list) and the REF cross-links carry no substrate dependency and are the patchable-now scope.

---

7.4 Answer to Success-Target Q14, Q16 (and feeds Q18)

Every specialized law's exact relationship to Đ37 is fixed (REF/NEW/CONTENT/CLEANUP/REGISTER/NONE), with wording, blocker, and acceptance test. The matrix shows what stays specialized (mechanisms) and what references Đ37 (the contract), satisfying Q14/Q16, and it surfaces the law-registration gap (Đ20/23/44/45 absent) and drift (Đ36/37/45) that feed the substrate-blocker list (doc 08, Q18).