90000x · 01 — Birth / Governance Reconciliation

Verdict: PASS (read-only verify). No rollback. No reapply. Case 3 Catalog Auto-Birth accepted as reconciled per the dedicated birth-pipeline audit pack ([[project_d36_nvsz_birth_pipeline_audit_qt_classification_2026_05_25]]).

Live evidence (2026-05-25)

Object kind	Identity	Present	Notes
entity_species id=51	SPE-NVS	✅	governed species for No-Vector Staging
collection_registry id=190	COL-IUS-001 (iu_staging_record)	✅	governance_role=governed, born
collection_registry id=191	COL-IUS-002 (iu_staging_payload)	✅	governance_role=governed, born
species_collection_map ids=172,173	SPE-NVS ↔ COL-IUS-001/002	✅	both bound
collection_registry_vector_policy (rows for 190+191)	sidecar, public schema	✅	vec=false, sem=false, has_explicit_policy=true
birth_registry row SPE-NVS	dot_origin=D36-Macro-A, status=born, certified=false	✅	clean origin
birth_registry row COL-IUS-001	dot_origin=SUSPECT:D36-Macro-A, status=born, certified=false	✅	accepted SUSPECT-prefix per [[feedback-suspect-prefix-is-accepted-pattern]]
birth_registry row COL-IUS-002	dot_origin=SUSPECT:D36-Macro-A, status=born, certified=false	✅	accepted SUSPECT-prefix

Why this is reconciled (not a defect)

• SUSPECT prefix is fn_validate_dot_origin's soft annotation when DOT code is absent from dot_tools whitelist. It never blocks INSERT and propagates one hop to birth_registry. TD-411 (canonical fix: dot_origin_whitelist table) is the long-term resolution, scheduled separately from 90000x.
• Case 3 Catalog Auto-Birth is the correct classification — registering a table into collection_registry/entity_species triggers fn_birth_registry_auto AFTER INSERT via trg_birth. That is not QT-001 (data-row backfill) and not QT-002 (data-row birth-first). It is the catalog-tier auto-birth pattern.
• certified=false is the normal initial state. Inspection→certification stamps (inspect_pen/stamp/gate/certified_at) are operator actions, deferred until first real cut completes successfully.

Half-born / orphan check

SELECT 'orphan_collections' check_name, count(*)::text result FROM collection_registry cr
LEFT JOIN birth_registry br ON br.entity_code = cr.collection_code
WHERE cr.id IN (190,191) AND br.id IS NULL
UNION ALL
SELECT 'half_born', count(*) FROM birth_registry
WHERE entity_code IN ('SPE-NVS','COL-IUS-001','COL-IUS-002')
  AND status NOT IN ('born','certified');

→ orphan_collections = 0, half_born = 0.

Documentation reconciliation

• Future macros must author Birth Execution Plan before any DDL when "Collection Birth Hard Gate" is invoked — see [[feedback-birth-execution-plan-hard-gate-precedes-apply]].
• Case 3 is accepted for NVSZ. No retroactive "QT-001/002 fix" is required and would in fact be misclassification.

Decision

No DDL, no DML, no rollback. NVSZ governance state accepted. Proceed to Phase B with confidence.