04 — Docs Patched / Created — Diff Manifest & Acceptance Check

All edits are additive (append-only sections; no prior content removed). KB revision shows the per-edit counter (storage artifact, not a semantic version bump).

4.1 Created — concept canon (4 docs, rev 1)

Doc	Carries	Blocker flags	Technical-deferred?
…/one-roof-governance-concepts/00-concept-canon-index.md	scope envelope, 18-concept inventory table, blocker summary, reading contract	SB-1/2/3, OP-B, C-4/5, L-1/2, H-1/2 (summary)	✅
…/01-governed-object-and-coverage-concepts.md	One-Roof; M-DEF-1,2,3,4,5,6,7,10; island; invariant v3; detection; anti-spam; readiness gate; §0-GOV	SB-1 (exception store), SB-3 (IU grain), SB-8 (detection), L-2 (Đ20)	✅ (per-card + summary)
…/02-open-axis-iu-and-dieu37-hub-concepts.md	M-DEF-8,9; IU first-class; Đ37 OWN/REFERENCE; specialized-law reference pattern	SB-2, SB-3 (axis); OP-B, C-4, SB-3 (IU)	✅
…/03-blockers-carried-forward-and-readiness.md	full blocker register; concept-GO vs later-NO-GO; deferred-technical declaration	SB-1..9, OP-B, C-1..6, H-1/2, L-1/2/3	✅ (whole doc)

4.2 Patched — Registries-Pivot OS Agency (6 docs, rev 1→2)

Each received one ## Round 4 One-Roof Governance Concept Patch (2026-06-01) section appended after its existing trailing content.

Doc	Concept refinement applied	M-DEF refs	§0-GOV/cross-link?	Blocker flag
00-master-design-v0.1.md	surface-is-governed-not-a-second-roof; accounting invariant = Coverage Invariant v3; count>1 dual-sense (UI vs governance); NEW registry = governed object	M-DEF-1,2,3,4,7,10	✅ canon cross-link	SB-1/2/3, OP-B, C-5, L-1/2
04-dynamic-drilldown-layer-model.md	count>1 = candidacy trigger not mandate; non-hiding owner-link-only inheritance	M-DEF-10, M-DEF-7, M-DEF-8/9	✅ canon	SB-2, SB-3
06-orphan-phantom-unmanaged-policy.md	birth precedence; governance-orphan vs anarchic + 12 gap types; island dual-channel; per-source-model phantom (L-3)	M-DEF-4, M-DEF-5	✅ canon	SB-4, SB-8, L-3
07-label-grouping-policy.md	grouping dimension = governed axis; Axis Registry; 50-ceiling = grouping-policy; SB-3 caveat	M-DEF-8, M-DEF-9	✅ canon	SB-2, SB-3
08-pin-ghim-policy.md	pin scope ⇒ Class 0 (user) vs governed (global/role/team); C-6 export crossover; M-DEF-6 exception	M-DEF-1, M-DEF-3, M-DEF-6	✅ canon	SB-1, SB-2, OP-B(if IU)
12-implementation-readiness-gate.md	RG1-8 = G-DESIGN instance of 4-phase gate; §0-GOV obligation; owner-per-scope; C-5 render	readiness gate, §0-GOV, M-DEF-3	✅ canon + §0-GOV block	SB-1/2, OP-B, L-1/2, C-5

4.3 Patched — IU foundation (1 doc, rev 1→2)

Doc	Concept refinement applied	Held / deferred	Blocker flag
iu-mow-mot-event-foundation-design.md	IU = first-class governed domain (concept); axes A/B/C are examples not a closed list; future IU axis = Axis-Registry row; non-exemptable IU invariants	OP-B (owner-binding NO-GO), C-4 (review_decision adapter), SB-3 (envelope generalization = IU technical design, DEFERRED), SB-1/2	✅ all flagged + "OUT OF SCOPE / DEFERRED" banner

4.4 Acceptance check (per mission §7 deliverable: "acceptance check that each doc carries its M-DEF references, its §0-GOV block, and its blocker flag")

Requirement	Result
Each patched/created doc carries its M-DEF references	✅ — see the "M-DEF refs" columns above; canon docs carry the full M-DEF-1..10 cards
§0-GOV block present where applicable	✅ — canon doc 01 §12 carries the full §0-GOV declaration template; Reg-Pivot 12 carries the §0-GOV obligation; all surface patches cross-link the canon §0-GOV
Each doc flags its blocker(s)	✅ — every section ends with an explicit Blockers line; canon doc 03 is the consolidated register
Technical implementation marked deferred	✅ — every section + every canon doc states "technical implementation DEFERRED"
No prior content deleted	✅ — append-only; verified the patch old_str anchors were the original trailing text, preserved intact
No version/status bump	✅ — no vX.Y/status line altered (doc 06)

4.5 Concept-patch verdict

APPLIED / GO. All 18 concept items (mission §3) are now carried in the canonical design layer: the full clause cards live in the new concept canon, and the directly-affected surface + IU canonical docs carry concept-patch sections that reference them and flag their blockers. No technical, apply, IU-surface, law, or enactment content was introduced.