03 — Patch Plan

3.1 Patch behavior rules (mission §6) — applied

Rule	How honored
Do not increment version numbers	No design vX.Y or status line changed. (KB storage revision is an automatic per-edit counter, not a semantic version — doc 06.)
Do not change enacted/draft status	Registries-Pivot stays "DESIGN-ONLY · canonical · NOT ratified"; IU foundation stays "DRAFT"; canon docs marked "CONCEPT-LEVEL · DRAFT · NOT ratified".
Do not run amendment/enactment workflow	None run.
Do not update normative_registry/law_catalog/governance_docs	None touched.
Do not cascade metadata updates	Only the edited docs' own revision advanced (unavoidable on edit).
Do not delete prior content	All patches are append-only sections; no prior text removed.
Add clear "Round 4 One-Roof Governance Concept Patch" sections	Every patched doc carries exactly such a section.
Mark blockers explicitly	Every section ends with a Blockers line; canon doc 03 is the full register.
Mark technical implementation as deferred	Every section + every canon doc states "technical implementation DEFERRED".

3.2 The two-layer patch strategy

Layer A — create the missing concept canon (knowledge/dev/design/one-roof-governance-concepts/, 4 docs). This is where the 18 concepts live in full (M-DEF cards, §0-GOV, Đ37 OWN/REF, blocker register). Rationale: the One-Roof concepts had no canonical home; putting them once in a canon (and having surfaces reference it) honors the Điều 37 anti-bloat principle and avoids duplicating clause text across 14 surface docs.

Layer B — patch the directly-affected existing canonical docs with concise concept sections that (a) state the specific refinement that doc needs, (b) cross-link the canon, (c) flag the relevant blockers, (d) declare technical impl deferred. Rationale: satisfies "real targets discovered + concept patches applied" without bloating or risking the shipped surface docs.

3.3 Per-touchpoint plan

Touchpoint	Layer	Concept(s) delivered
canon 00 index	A	scope envelope, concept inventory (18), blocker summary, reading contract
canon 01 governed-object & coverage	A	One-Roof; M-DEF-1/2 (Class 0, profiles); M-DEF-10 (count>1); M-DEF-4/5 (orphan/anarchic, 12 gap types); island; M-DEF-3 (ownership scopes); M-DEF-6 (exception); M-DEF-7 (grain, invariant v3, non-hiding); detection; anti-spam; readiness gate; §0-GOV
canon 02 open-axis/IU/Đ37	A	M-DEF-8/9 (axis, Axis Registry); IU first-class concept (OP-B/SB-3 held); Đ37 OWN/REFERENCE; specialized-law reference pattern
canon 03 blockers & readiness	A	SB-1/2/3, OP-B, C-1..C-6, H-1/2, L-1/2/3, SB-4..9; concept-GO vs later-NO-GO; deferred-technical declaration
Reg-Pivot 00 master	B	surface-is-governed; invariant↔coverage-invariant-v3; count>1 dual-sense; NEW registry = governed object
Reg-Pivot 04 drill-down	B	M-DEF-10 candidacy-not-mandate; M-DEF-7 non-hiding inheritance
Reg-Pivot 06 orphan/phantom	B	M-DEF-4 birth precedence; M-DEF-5 anarchic + 12 gap types; island dual-channel; L-3 phantom
Reg-Pivot 07 label/grouping	B	M-DEF-8/9 axis + Axis Registry; 50-ceiling = grouping-policy; SB-3 caveat
Reg-Pivot 08 pin	B	M-DEF-1 Class 0 by scope; C-6 crossover; M-DEF-6 exception
Reg-Pivot 12 readiness	B	4-phase gate; §0-GOV; M-DEF-3 owner-per-scope; C-5 render
IU foundation	B	IU first-class concept; axes are examples; OP-B + SB-3 + C-4 HELD/DEFERRED

3.4 Forbidden list for this patch (carried verbatim from mission §4)

Do NOT patch or design: PG schema implementation · DOT implementation · scanner SQL/view/function · issue/event registration · apply/remediation binding · object/axis ownership table design beyond approved concept references · IU surface/binding technical design · production UI/API/route · law enactment · normative_registry/law_catalog/governance_docs · version numbers/status · anything that pretends blockers are solved.

All honored — see doc 06 forbidden-compliance matrix.