Stage 1 — 06 fn_birth_registry_auto Integration Decision (Supertrack F)

Decision: Option A — PARITY-GUARD-ONLY (no behavioral change to the live gateway in Stage 1)

The live trigger gateway fn_birth_registry_auto was left byte-identical (norm-md5 c022f849c2c7d57a720c4cc172789d70). Stage 1 adds the contract + shared functions but does NOT wire them into the realtime trigger. Full integration is staged for Stage 2 under T2/operator review.

Why Option A and not B/C now

Option	What it does	Why deferred
A — parity guard only (CHOSEN)	gateway unchanged; prove contract parity	zero risk to QT-002 live path
B — wrap policy only	gateway calls fn_birth_policy_decision	would STOP DEFERRED births = live behavior change; needs operator review
C — full thin-wrapper	gateway = thin wrapper over the 3 fns	larger behavior surface; T2 review + setup-DOT strip required

The forbidden list prohibits CREATE OR REPLACE fn_birth_registry_auto from DOT source; Stage 1 honours the spirit by not rewriting the live gateway at all. Per completion contract, a risky function integration that must wait for T2/operator review while all safe branches complete = the expected PARTIAL-on-that-branch; everything else PASS.

Parity status — v_birth_registry_auto_stage1_parity_status

Class	Live behavior	Stage 1 contract	Parity
EXEMPT	SKIP (coverage_status LIKE BIRTH_EXEMPT%)	BIRTH_EXEMPT (skip)	MATCH
REQUIRED	BIRTH	BIRTH_REQUIRED (birth)	MATCH
DEFERRED	BIRTH (live gateway has no defer guard)	BIRTH_DEFERRED (skip)	DIVERGENT — contract stricter
UNREGISTERED	BIRTH (governance_role=excluded)	UNKNOWN_BLOCK	DIVERGENT — contract stricter

The two divergences both reduce births (contract ≤ live). Stage 2 must decide, under operator review, whether to adopt the stricter DEFERRED/UNKNOWN behaviour in the live gateway (Option B/C). Until then there is no behavior drift.

No-go guard — v_birth_registry_auto_no_go_guard (4/4 PASS, live)

gateway_norm_md5_unchanged (c022f849) · gateway_still_has_exempt_guard · gateway_does_not_call_stage1_fns · contract_drift_ok.

Integration decision view — v_birth_registry_auto_integration_decision

chosen_option = A_PARITY_GUARD_ONLY · applied_now = false · options B/C = deferred_to_stage2. The exact Stage 2 integration packet is report 08 + BIRTH_STAGE2_QT001_METADATA_BACKFILL_REPAIR_PACKET.md (and the setup-DOT strip from the Stage 1 packet §3).