01 — State Recovery (Patch Canonical Design One-Roof Concepts, Round 4, 2026-06-01)
01 — State Recovery
Per mission §1, state was recovered from KB before any patching. No patching began before this recovery.
1.1 Sources read (mission §1 mandatory list)
| # | Source | Read | Key takeaway |
|---|---|---|---|
| 1 | …/one-roof-governance-law-hardening-finalization-round4-2026-06-01/ (00,02,06,08,10,11,12,13 in full; 01–13 indexed) |
✅ | Controlling input. PASS + CONDITIONAL GO. Carries M-DEF-1..10, §0-GOV, count>1 rule, Đ37 hub decision, SB-1..9, Red-Team v3. |
| 2 | …/gpt-review-round4-one-roof-governance-ready-for-concept-design-patch-2026-06-01.md |
✅ | External reviewer concurs: concept patching OK; technical/enactment/IU-surface/remediation NOT. |
| 3 | …/one-roof-governance-hardening-revision-all-domains-all-axes-2026-06-01/ (indexed; 05 read via search) |
✅ | Round-3 source of M-DEF-1..9, Open-Axis, IU first-class, Đ37 hub. |
| 4 | …/one-roof-governance-clause-review-hardening-2026-06-01/ (indexed) |
✅ | Round-2 adversarial clause hardening. |
| 5 | …/one-roof-governance-decision-pack-2026-06-01/ (01/02 read via search) |
✅ | Round-1 governed-object contract; ownership is relational (no owner_gov_code column). |
| 6 | knowledge/dev/laws/prompt-muc-tieu-mo-for-claude-code.md |
✅ (sliced) | House standard: no_hardcode_absolute, discover_first_reuse_first, five-layer sync, Design-Only Macro Mode = exactly this session's mode. |
1.2 Verdict: Round 4 is the latest controlling input
The lineage is Round 1 (Decision Pack) → Round 2 (Clause Review & Hardening) → Round 3 (Hardening Revision, All Domains/All Axes) → Round 4 (Finalization). Round 4 doc 00 §0.1 records its own verdict as PASS / CONDITIONAL GO, doc 13 confirms acceptance, and doc 12 lists this exact macro as Prompt 1 (the GO path). The GPT review (source 2) independently confirms readiness for the concept tier. No later round exists (KB listing of …/architecture/ shows Round 4 as the most recent One-Roof package, dated 2026-06-01). Therefore Round 4 controls, and this session is its true continuation.
1.3 What Round 4 ALLOWED (this session's scope envelope)
Round 4 doc 11 §11.2 authorizes patching exactly these concept/principle canonical design docs, each carrying doc 10's clause cards and flagging its blockers:
- One-Roof principle (+ no-local-island)
- Governed-object contract (M-DEF-1/2 + 13 classes + Class 0)
- count>1 relevance rule (M-DEF-10)
- Governance-orphan / anarchic (M-DEF-5 + 12 gap types)
- Open-axis model + Axis Registry (M-DEF-8/9) — carry SB-3 caveat
- IU governance-coverage concept (excluding owner-binding)
- Coverage invariant v3 (M-DEF-7)
- Ownership / responsibility-scope (M-DEF-3)
- Governed-exception contract (M-DEF-6)
- Detection obligation + anti-spam
- Readiness gate (4 phases) + §0-GOV hook
- Đ37 hub clauses (OWN list) + specialized-law reference pattern
1.4 What Round 4 FORBADE (held to later tiers)
Round 4 doc 11 §11.3 + GPT review "forbidden" list:
- Object/axis-grain remediation binding (the apply DOT writing owner edges) — SB-1/SB-2.
- IU owner assignment / IU surface docs — OP-B.
- IU axis-envelope generalization (substrate) — SB-3.
- Any law file (Đ37/31/32/35/44/45 text) — content-only L-1/L-2 first, then a separate law-patch macro.
- Anything that enacts, version-bumps, approves, mutates PG/Directus/Qdrant/Nuxt, or changes routes/UI/schema.
1.5 Blockers to carry forward (named in the controlling input)
From Round-4 docs 02 (closure ledger), 08 (SB-1..9), 11 (GO/NO-GO):
- Substrate: SB-1 (governance APR action-types), SB-2 (object/axis ownership edge), SB-3 (IU 3-axis envelope hardcode), plus SB-4 (event/issue types), SB-5 (enact handlers), SB-6 (sovereign sign-off), SB-7 (audit loop dormant), SB-8 (coverage rows), SB-9 (law-registration drift).
- Council/human (8-item surface): C-1 (object-edge table), C-2 (APR action-type bundle), C-3/OP-B (IU owner), C-4 (
review_decisionadapter), C-5 (GOV-MOUT/render owner), C-6 (shareable-personal boundary), H-1 (enactment phase), H-2 (OP-B ratification). - Law-drift: L-1 (enacted-law drift), L-2 (register Đ20/23/44/45), L-3 (phantom wording).
Each is carried into the concept canon (doc 03) and flagged in every patched section. None blocks the concept tier; each blocks a later tier.
1.6 Live-substrate facts reused (read-only, as recorded in Round-4 doc 08, not re-queried this session)
The concept patch relies on these already-verified live facts (it does not re-assert them as new evidence): no GOV-IU agency; governance_relations CHECK ∈ {law,agency}; apr_action_types=6; os_proposal_approvals=0; iu_three_axis_envelope hardcodes 3 axes (216 rows); information_unit=219 all conformance_status='open', owner_ref free-text; normative_registry=47 lacking Đ20/23/44/45; system_issues.template_gap=182,378. These ground the blocker flags. (A fresh read-only PG re-verification was deemed unnecessary for a concept patch and would have added no concept content; the Round-4 read-only snapshot is < 1 day old.)