07 — Safety Audit (Supertrack G)

All checks live-verified 2026-06-06 post-apply. Consolidated guard view: v_birth_stage0_regression_guard = 10/10 ALL_PASS.

Audit item	Evidence	Result
No dot-birth-trigger-setup / backfill executed	Only froze them; originals never run; wrappers exit 3	PASS
No birth gateway function changed	fn_birth_registry_auto guard PASS, markers intact, norm-md5 still c022f849…	PASS
No trigger changed	trigger_guard_alerts (tga) = 129 unchanged; fn_birth_registry_auto on 166 triggers (unchanged); all_birth_triggers 213	PASS
No source data changed	birth_registry 1,210,834→1,210,839 (linear realtime growth, no spike); only views + 2 file renames	PASS
No birth explosion recurrence	+5 rows / ~30 min; gateway still skips EXEMPT/DEFERRED	PASS
No owner/vote/RP/REALRUN/event mutation	apr_approvals = 42 unchanged; no axis/event/RP tables touched	PASS
OOM safe	postgres running, RestartCount=0, 50-day uptime, no OOM in this session; all reads light (catalog + count + view DDL)	PASS
Rollback exists for any filesystem change	BIRTH_STAGE0_FREEZE_ROLLBACK.md + byte-identical quarantine (md5 verified); 99_rollback_views.sql for views	PASS
birth-neutral DDL	before==after on both apply files (1,210,839==1,210,839)	PASS

Note: docker inspect postgres shows a sticky State.OOMKilled=true flag, but the container has not restarted (RestartCount=0) and has run since 2026-04-17; dmesg shows no recent OOM. The flag is historical, not from this session.

Completion: every forbidden side effect was avoided; all mutations are reversible and birth-neutral.