11 — GO / NO-GO for Next Step (Branch K)

11.1 Decision

CONDITIONAL GO — confirmed and tightened from Round 3. Round 4 does not raise the bar back to NO-GO: all Tier-1 wording blockers are resolved, all open questions are closed/classified, all-domain coverage and the count>1 rule are proven, and Red-Team v3 passes at 100% caught / 90.6% auto-remediable. What remains are the same named substrate/council/human prerequisites — none of which block the concept-level canonical design patch.

Track	Decision	Gate
Concept / principle canonical design docs	GO — patch now	carry M-DEF-1..10 + §0-GOV + flag blockers
Apply / remediation-binding design docs	NO-GO	until SB-1 (APR action-types) + SB-2 (object/axis edge) + SB-3 (IU axis envelope)
IU surface / owner-binding design docs	NO-GO	until OP-B (C-3 owner) + C-4 (review_decision ruling)
Law patch (touching law files)	NO-GO	until L-1 (drift) + L-2 (register Đ20/23/44/45), content-only
Law enactment	NO-GO	separate human phase: SB-5 (handlers) + SB-6 (sovereign sign-off)

---

11.2 What CAN be patched now (concept GO scope — exact)

Patch these concept/principle canonical design docs, each carrying doc 10's clause cards and flagging its blocker:

1. One-Roof principle statement (+ no-local-island).
2. Governed-object contract (M-DEF-1/2 + 13 classes + Class 0).
3. count > 1 relevance rule (M-DEF-10) — NEW.
4. Governance-orphan / anarchic definition (M-DEF-5 + 12 gap types).
5. Open-axis model + Axis Registry (M-DEF-8/9) — carry the SB-3 caveat.
6. IU governance-coverage concept (IU-GOV-1..5) — excluding owner-binding (OP-B).
7. Coverage invariant v3 (M-DEF-7 + axis/IU grain).
8. Ownership / responsibility-scope model (M-DEF-3).
9. Governed-exception contract (M-DEF-6).
10. Detection obligation + anti-spam (Đ37 §4.17 + §4.17-bis).
11. Readiness gate (4 phases) + §0-GOV hook.
12. Điều 37 hub clauses (doc 06 OWN list) + the specialized-law reference pattern (doc 07 REF rows).

These carry no substrate dependency — they are definitions/contracts the system reconciles against.

---

11.3 What must NOT be patched (held)

• Object/axis-grain remediation binding (the apply DOT writing owner edges) — needs SB-1/SB-2.
• IU owner assignment / IU surface docs — needs OP-B.
• The IU axis-envelope generalization (substrate) — IU technical design after OP-B (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.

---

11.4 Blockers (consolidated)

ID	Blocker	Class	Decision owner	Blocks
SB-1 / C-2	4 governance APR action-types	substrate + council	COUNCIL	apply (PROPOSE)
SB-2 / C-1	object/axis ownership edge (new table)	substrate + council	COUNCIL	apply (APPLY)
SB-3	IU 3-axis envelope hardcode	substrate	IU design (post-OP-B)	open-axis at IU substrate
OP-B / C-3	IU family owner assignment	council + human	COUNCIL + sovereign	IU surface/owner-binding
C-4	review_decision adapter ruling	council	COUNCIL	IU approval routing
C-5	GOV-MOUT activation / render owner	council	COUNCIL	render-binding
L-1	enacted-law drift (Đ36/37/45)	law-drift	NRM-SYS	law patch
L-2	register Đ20/23/44/45	law-drift	NRM-SYS	law patch
SB-5 / SB-6 / H-1	enact handlers + sovereign sign-off	human	sovereign	enactment

Net council/human decision surface = 8 (C-1..C-6, H-1, H-2), each with a recommended default (doc 02).

---

11.5 Unresolved questions (now all classified — none vague)

Per doc 02: 11 resolved/design-default · 6 council · 2 human · 3 substrate · 3 law-drift · 2 defer-safe. Zero unclassified. The council/human need only rule on the 8-item surface in §11.4; everything else proceeds on a firm default or a named blocker with an upgrade path.

---

11.6 Exact next macro

Primary (GO): PATCH_CANONICAL_DESIGN_ONE_ROOF_CONCEPTS_ROUND4 — patch the 12 concept docs in §11.2 into the canonical design package, carrying M-DEF-1..10 + §0-GOV, flagging SB-1/2/3 + OP-B, no apply/IU-surface/law-file/enactment. (doc 12 prompt 1.)

Parallel, non-blocking:

• DRAFT_SUBSTRATE_DESIGN_SB1_SB2_SB3 — design-only (read-only/rollback rehearsal) for the action-types + object-edge table + IU axis store. (prompt 5.)
• DECIDE_OP_B_IU_OWNER — council packet to assign IU owner + rule on review_decision. (prompt 6.)
• CONTENT_ONLY_LAW_CLEANUP_AND_REGISTER — L-1/L-2 drift + registration. (prompt 4.)

---

11.7 Answer to Success-Target Q20

"Is it safe to move to canonical design doc patching? If yes, what scope?" → CONDITIONAL GO.

• YES for the concept/principle scope (§11.2) — the legal/design layer is now tight enough: hardened definitions, closed open-question ledger, all-domain proof, count>1 rule, 100%-caught red-team.
• NO for apply/remediation binding (SB-1/2/3), IU surface (OP-B), law files (L-1/L-2), and enactment (SB-5/6) — each a named, detected, upgrade-pathed prerequisite.

This is a valid PASS with CONDITIONAL GO. No major legal ambiguity remains unclassified.