05 — Blockers Carried Forward

Per mission §3.18, every prerequisite/blocker is carried forward explicitly. None is solved here. Every one is open. Each blocks a later tier, not the concept tier. Full evidence: Round-4 docs 02/08; canonical home: concept-canon doc 03.

5.1 Substrate blockers (hard apply-blockers in bold)

ID	Blocker	Live evidence	Holds tier	Carried in
SB-1	Missing governance APR action-types (assign_governance_owner / grant_governance_exception / delegate_authority / assign_axis_owner)	apr_action_types=6, none governance; amend_law/enact_nrm unimplemented	apply (PROPOSE)	canon 01 §7, 03; Reg-Pivot 00/08/12
SB-2	Object/axis ownership edge un-expressible	governance_relations CHECK ∈ {law,agency}; 8 edges agency→law	apply (APPLY)	canon 02 §2, 03; Reg-Pivot 00/04/07/08; IU
SB-3	IU iu_three_axis_envelope hardcodes 3 axes in DDL	columns axis_a/b/c_*; 216 rows; 4th axis ⇒ ALTER	open-axis at IU substrate	canon 01 §8, 02 §3, 03; Reg-Pivot 00/07; IU
SB-4	No governance/coverage/axis/orphan/anarchy/island/exception event-type domain	event_type_registry; mother.* inactive; system_issues free-text	detection routing	canon 03; Reg-Pivot 06
SB-5	Law-enact handlers unimplemented	amend_law/enact_nrm handler_ref='unimplemented'; enact-APR 204–210 rejected	enactment	canon 03
SB-6	No sovereign sign-off	os_proposal_approvals=0; apr_approvals=42 all S178	commit/enactment	canon 03
SB-7	Governance audit loop dormant	governance_audit_log=1 stale	central audit (impl)	canon 03
SB-8	No coverage-required rows for the new scanner	dot_coverage_required=11 (no governance.coverage/axis/iu)	scanner design	canon 01 §9, 03; Reg-Pivot 06
SB-9	Law-registration gap + drift	normative_registry lacks Đ20/23/44/45; Đ36/37/45 drift; stale law_catalog/governance_docs	law-file patch	canon 03 (= L-1/L-2)

5.2 Council / human decision surface (8 items)

ID	Decision	Recommended default	Holds tier
C-1	object/axis ownership edge: new table vs widen CHECK	new governance_object_ownership table	apply
C-2	governance APR action-type bundle	one bundle of 4 (1 handler + 3 council-review)	apply
C-3 / OP-B	IU family accountable owner per scope	policy→COUNCIL; substrate/health→KG-SYS+SIV; exec→DOT; render→MOUT(TTL); law→NRM-SYS	IU surface / owner-binding
C-4	review_decision adapter vs full Đ32	record as governed approval-adapter exception (replacement_plan → Đ32)	IU approval routing
C-5	render owner: COUNCIL delegation vs GOV-MOUT activation	delegation now (TTL); GOV-MOUT activation end-state	render-binding
C-6	shareable-personal boundary (A2) + legacy-bypass deadline (A3)	governed at export/share; 60 days	(proceed on default)
H-1	how clauses become enacted law	separate human-ratification phase	enactment
H-2	OP-B owner-binding ratification	sovereign ratifies C-3 into governance_registry	IU owner-binding (live)

None of the 8 blocks the concept tier. Every one blocks a later tier and carries a recommended default (Round-4 doc 02).

5.3 Law-drift blockers (content-only; block a law patch, not this concept patch)

ID	Blocker	Holds tier
L-1	Enacted-law drift: Đ45 ban_hanh=false leftover; Đ36 v4.0/v5.0; Đ37 v3.3 vs live columns	law-file patch
L-2	Register Đ20/23/44/45 in normative_registry	law-file patch + clauses citing them
L-3	Phantom definition wording (per-source-model)	law-tier wording

5.4 The explicit prerequisite flags requested by the mission (§3.18) — confirmed present

Mission flag	Where carried
SB-1: missing governance APR action types	canon 01 §7, 03; Reg-Pivot 00/08/12 ✅
SB-2: object/axis ownership edge missing	canon 02 §2, 03; Reg-Pivot 00/04/07/08; IU ✅
SB-3: IU three-axis envelope hardcoded	canon 01 §8, 02 §3, 03; Reg-Pivot 00/07; IU ✅
OP-B: IU owner unassigned	canon 00, 02 §3, 03; IU; Reg-Pivot 00/08 ✅
C-5: GOV-MOUT/display owner unresolved	canon 03; Reg-Pivot 00/12 ✅
L-1/L-2: law drift and registration gaps	canon 03; Reg-Pivot 00/12; IU ✅
H-1/SB-5/SB-6: enactment/sign-off path	canon 00, 03 ✅

5.5 Non-solving guarantee

No section of any patched or created doc claims a blocker is solved. The deferred-technical declaration (canon doc 03 §3.7) enumerates everything that remains out of scope: PG schema, DOTs, scanner SQL, issue/event registration, apply/remediation binding, IU surface/owner/axis-envelope, production UI/API/route, law enactment/version bump/approval. The concept patch is a design-readiness step, not a buildable design.