10 — Cross-Layer Impact (Supertrack J)

Guard v_qt001_apply_hardening_cross_layer_guard — all 9 pass:

Assertion	Result
stage0_freeze_intact	pass — v_birth_stage0_still_enforced_guard 5/5; danger DOTs frozen 2/2
stage1_gateway_md5_unchanged	pass — fn_birth_registry_auto norm-md5 = c022f849c2c7d57a720c4cc172789d70
gateway_contract_all_ok	pass — v_birth_gateway_contract_integrity_dashboard.all_ok (5/5 fns)
no_new_trigger_tga_129	pass — trigger_guard_alerts = 129 (only CREATE TABLE/FUNCTION/PROCEDURE/VIEW + CREATE INDEX; no CREATE TRIGGER, no ALTER TABLE)
authority_apr_42	pass — apr_approvals = 42
target_births_8	pass — 5 target collections = 8 births
qt001_apply_origin_births_0	pass — 0 births with origin STAGE2.5:dot-birth-qt001-apply
exempt_deferred_register_skips	pass — fn_birth_register still skips BIRTH_EXEMPT/BIRTH_DEFERRED
gateway_fn_body_unchanged	pass — no new object redefines fn_birth_registry_auto

Layer-by-layer

• Stage 0: untouched; freeze + gateway guard intact.
• Stage 1: gateway function body and the 5 tracked-fn hashes unchanged; fn_birth_register/fn_birth_policy_decision/fn_birth_resolve_identity unchanged.
• QT-002 (realtime): no worse — no trigger or gateway change; new objects are inert until an execute permit is opened.
• EXEMPT/DEFERRED: no direct birth path; the writer only proceeds for BIRTH_REQUIRED + eligible + apply_safe.
• Authority: apr unchanged (42); no owner/vote/RP/REALRUN/event/UI mutation.
• RP clean count: untouched except the deliberate rehearsal (fully rolled back).
• OOM: PostgreSQL 16.13; only metadata DDL + bounded reads; no heavy unbounded scan committed; container healthy.

ALTER-TABLE avoidance note

All v2 table constraints are inline in CREATE TABLE; uniqueness via CREATE [UNIQUE] INDEX. This keeps evt_trigger_guard_ddl (fires on CREATE TRIGGER / ALTER TABLE) from triggering, so tga stayed 129.