04 — Required Collection Preflight (Supertrack D)

All 74 BIRTH_REQUIRED collections recomputed and made explainable. Every one is PASS or BLOCKED_WITH_REASON.

Preflight result over 74 REQUIRED

Bucket	Count	Note
PASS (table + policy REQUIRED + identity ELIGIBLE)	68	backfill-eligible by preflight
BLOCKED_NO_TABLE	2	iu_staging_payload, iu_staging_record (identity classified column, but no PG table)
BLOCKED_UNCLASSIFIED	4	apr_request_types, binding_registry, nrm_approval_rules, nrm_doc_type_config (needs-owner)
Total	74	every collection explained, none NULL

v_birth_stage2_required_no_go_guard = 5/5 PASS (every_required_pass_or_blocked_with_reason=0 NULLs, pass=68, no_table=2, unclassified=4, total=74).

Per-collection gates checked

table_exists · native status column · birth trigger attached · policy decision (REQUIRED) · identity status · existing birth coverage · duplicate risk. Live view: v_birth_stage2_required_collection_preflight. Gaps: v_birth_stage2_required_gap_inventory (the 6 non-PASS).

The 2 no-table REQUIRED

iu_staging_payload, iu_staging_record — identity already classified (column/staging_*_id, migration_seed) but no PG table exists, so they cannot be backfilled. Disposition: action-pack — either create the staging tables (then QT-002 realtime + QT-001 backfill cover them) or reclassify coverage. Not created here (table creation is QT-003R / owner scope, outside QT-001 backfill). They are excluded from backfill scope, as the Stage 1 packet requires.

Native status gap

20 of 74 REQUIRED lack a native status column. This is acceptable for birth (birth row uses default; lifecycle/death is QT-006, a separate program). Not coupled into QT-001.

Duplicate risk

0 in the entire delta scope: synthetic targets key on unique id; apr_action_types keys on unique PK action_code. Code-strategy collections with non-unique code (checkpoint_instances, etc.) all have expected_delta=0 (already covered), so no risk surfaces.