Stage 1 — 08 Stage 2 QT-001 Metadata Backfill Repair Packet (Supertrack H)

Full packet: knowledge/dev/architecture/BIRTH_STAGE2_QT001_METADATA_BACKFILL_REPAIR_PACKET.md. Live dashboard: v_birth_stage2_qt001_readiness_dashboard. Summary below; no backfill executed.

Readiness dashboard (live)

Metric	Value
birth_required_total	74
identity_resolvable_now	31
identity_unclassified_blockers	43
admission_permit_table	present
open_permits	0
backfill_ledger_table	present
shared_register_fn	present
qt001_gate	BLOCKED_UNTIL_43_IDENTITIES_RESOLVED_AND_PERMIT_OPENED

Metadata compatibility matrix (BIRTH_REQUIRED = 74)

• 27 column + 4 synthetic = 31 compatible now; 43 unclassified = broken (classify first).
• This supersedes the older "14 compatible / 22 broken (governed=36)" script-compatibility figure — the live metadata-driven cut over the full REQUIRED scope is 31/43. Live evidence wins.
• Native status col 54/74; birth-trigger gap = 2 (no PG table: iu_staging_payload, iu_staging_record) — note prior docs said 5; live recomputation = 2 (0 table-but-no-trigger, 72 have trigger). Governed subset = 35 REQUIRED (+1 EXEMPT = 36 governed).

Plan/apply split (replaces frozen direct-INSERT backfill)

• dot-birth-backfill-plan (read-only): assert policy/identity, count missing via anti-join on resolved entity_code, write a birth_backfill_ledger planned row.
• dot-birth-backfill-apply (gated writer): requires OPEN permit + contract all_ok + identity classified; iterates bounded batch transactions calling fn_birth_register(..., p_dry_run := false); updates ledger. Never CREATE OR REPLACE FUNCTION; never touches gateway/triggers.

Acceptance gates

dry-run plan → operator reconciles planned vs source → batched apply → rerun-delta = 0 (idempotent) → no self-certify (independent T2 reviewer) → birth-neutral except intended rows, tga unchanged, gateway norm-md5 c022f849 unchanged.

Next macro

BIRTH_STAGE2_QT001_IDENTITY_CLASSIFICATION_AND_METADATA_BACKFILL.