03 — Ownership-Seed Commit Plan (staged, BLOCKED) & Blocker

Status: STAGED, NOT EXECUTED. Blocker = os_proposal_approvals = 0.

The blocker (single sentence)

The 30-anchor ownership seed persistently asserts sovereign accountability and lowers governed coverage 210→0 in the production directus database; that act is gated on human L2+L4 ratification, whose machine-checkable proxy os_proposal_approvals is 0 live. No other condition blocks it.

The exact committable artifact (proven by F-5/F-6)

30 rows into governance_object_ownership = 5 groups × 6 active scopes, all object_type='group', owner_kind='accountable', is_inherited_anchor=true, lifecycle_status='active'. Per-group FK-valid accountable owner (rehearsal-proven mapping):

Group	Children	Accountable owner
GRP-GOVERNANCE	16	GOV-COUNCIL
GRP-REGISTRY	14	GOV-KG-SYS
GRP-AI	1	GOV-DOT
GRP-BUSINESS	2	GOV-MOIT
GRP-WORKFLOW	2	GOV-DOT
Total	35	30 anchors (5×6)

Depth-1 containment fans each group anchor to its children → all 35 objects × 6 scopes = 210 cells covered → gap 0.

Provenance binding (honest, ratification-bound)

The committable script sets, per row:

• created_by = 'F6_OWNERSHIP_SEED_COMMIT' (greppable rollback key),
• approval_ref = :ratified_apr (bound to the ratified approval code, e.g. APR-BOOT-AUTHMODEL-1),
• source_design_ref = 'F6-anchor-ratified'.

The approval_ref column exists (verified live) — the seed is provenance-bound to the actual ratification, not to a fabricated test marker. This is why the seed should be committed under Path A (ratified) and not under a test label.

Self-guarding execution

sql/commit_ready_f6_ownership_seed.sql aborts the whole transaction unless, at run time:

• os_proposal_approvals ≥ 1, and
• pre-insert gap = 210, ownership = 0, conflict = 0, and
• post-insert exactly 30 rows, gap = 0, conflict = 0.

So even if run prematurely, it fails closed — it cannot commit while the gate is shut.

Expected deltas on an authorized COMMIT

Metric	Before	After
governance_object_ownership	0	30
v_object_owner_gap	210	0
v_object_owner_conflict	0	0
event_outbox (governance)	0	0
system_issues	(baseline)	unchanged
ruleset / candidate / scan_run / worker_cursor	0	0
os_proposal_approvals	≥1	unchanged
dot_tools	309	309

What is NOT in the plan (forbidden / unnecessary)

No ruleset seed, no candidate seed, no scan_run seed, no event/issue/log seed, no worker activation, no Directus/Qdrant/Nuxt write. Coverage is computed by read-only views; nothing needs to run.