07 — Governance Row Bridge & OSPA Approval Packet

Live governance state (re-verified 2026-06-03)

Object	Count
governance_object_ownership	0
ospa (active ownership pairs)	0
governance_responsibility_scope	6
governance_candidate_object	0
governance_candidate_state	0
candidate_scan_run	0
governance_ruleset	0
gov_worker_cursor	0
v_governance_object_inventory	35 (object_type distinct = 1, collection grain)
v_object_owner_gap	210

Production governance = inert skeleton, collection-grain only. No DOT row or pivot row is a governance object today; born DOTs never enter the inventory; owner_gap = 35 collections × 6 scopes = 210.

Can the row-level bridge be made visible now (read-only)?

Yes, technically — a read-only v_governance_row_object_inventory / v_governance_row_object_gap could be applied as inert views (like P5 in the prior package). But it was NOT applied this run because the authorized scope was P1/P2/FS-load/P6 only (P5 explicitly excluded). The P6 guard was therefore wired to the existing v_object_owner_gap instead.

Does OSPA / human approval still block?

Yes. ospa = 0 ⇒ governance L2 rollout is NO-GO. This is a human L2/L4 decision, unchanged by this macro. The row-bridge would make DOT/pivot rows visible as candidate governance objects, but operationalizing ownership still requires ospa ≥ 1.

Answers to the required questions

• Can row-governance bridge be visible now? Yes as inert read-only views; deferred (out of scope).
• Does a DOT row become a governance object? Not today (inventory is collection-grain, object_type=1). The row-bridge would add row grain.
• Does owner-gap detect a DOT row with no owner? Not today; it detects collection×scope gaps (210). Row-grain gap requires the bridge.
• Does dot-pivot-update stay blocked until governed? Yes — fn_preflight_guard BLOCKs on dot_pivot_update_not_governed=1 independently of governance rollout.
• Exact next human step? Approve OSPA seeding (ospa ≥ 1) at L2/L4, OR authorize applying the read-only row-bridge views for visibility-only.

OSPA approval packet (for L2/L4 owner)

Field	Content
What needs approval	Seed ≥1 governance_object_ownership row (ospa ≥ 1) to open L2 rollout; and/or authorize read-only row-bridge views
Why	Unblocks governance ownership operationalization; makes DOT/pivot rows governable at row grain
Risk of not approving	Born DOTs remain ungoverned; owner_gap stays at collection grain; dot-pivot-update and the 16 FILE_NO_REGISTRY cannot be lawfully onboarded into governance
Rollback	Delete seeded ownership rows; DROP VIEW the row-bridge views (inert)
Expected result after approval	ospa ≥ 1 → governance_gate_ospa dimension flips CLOSED→OPEN; candidate scan can populate
How to verify	SELECT * FROM fn_preflight_guard() WHERE check_name='governance_gate_ospa' shows status OPEN; v_object_owner_gap begins to close

No governance object was created or mutated this run.