06 — Entry == Exit / Rollback Verification

Transaction ended in ROLLBACK (no COMMIT in script). Verified on two independent channels.

Channel A — same psql session (entry vs exit)

ownership: 0 → (in-txn 2) → 0 (Δ0). gap: 210 → (207) → 210 (Δ0). effective_owner: 0 → (4) → 0 (Δ0). conflict: 0 → 0 → 0 (Δ0). event_outbox(governance): 0 → 0 → 0 (Δ0). The in-txn rows genuinely existed (own=2, gap=207) then vanished on rollback — a real transaction, not a no-op.

Channel B — independent query_pg (post-rollback)

own=0, gap=210, eo=0, conflict=0, inv=35, cont=35, gov_emit=0, cand_state=0, ruleset=0, worker_cursor=0, appr=211, apr_appr=42, ospa=0, dot_tools=309, gov_relations=8, idle_in_txn=0. Every value equals preflight baseline.

In-flight abort gates — none triggered

gap never >210 (peak 207); owner rows never >2; no event_outbox row (govemit_in_txn=0); no system_issues from us (no trigger + rollback); no worker cursor advance; no DOT/event/handler activation; no txn failed-state outside savepoints; idle_in_txn=0 after.

Out-of-scope drift

system_issues advances organically (199,455 at preflight), not attributable to F-5 (ownership table has no trigger writing to it, and txn rolled back). All governance-controlled counters exactly entry==exit.

Verdict: Entry==Exit PROVEN on both channels. Zero persistent mutation. No COMMIT.