Birth Stage 2 QT-001 — 00 README First
Birth Stage 2 — QT-001 Identity Classification + Metadata Backfill Repair — 00 README First
Date: 2026-06-06 · Mode: EXECUTION (principal-delegate) · Status: PARTIAL (all safe branches complete; real backfill apply deliberately NOT committed — gated by independent T2 review + owner permit per packet section 7).
Live mutation: YES, additive + reversible only. Committed: identity classification metadata for 39 collections (collection_registry.birth_code_*), 5 birth_backfill_ledger PLAN rows (dry_run), 25 additive views, 1 cosmetic view re-alias. NOT committed: any birth_registry row (net DB births by this macro = 0), any gateway/trigger/function-body change, any real backfill.
What changed (one line)
QT-001 moved from BLOCKED_UNTIL_43_IDENTITIES_RESOLVED to 70/74 identity-resolvable, full dry-run proven, apply rehearsed (137 births, rerun-delta=0, rolled back), apply path action-ready and fail-closed — without committing a single backfill birth.
Outcome vs goal
From BIRTH_GATEWAY_SSOT_RUNTIME_CONTRACT_LIVE + SHARED_POLICY_IDENTITY_REGISTER_FOUNDATION_READY to QT001_IDENTITY_CLASSIFIED (70/74) + METADATA_PREFLIGHT_READY + PLAN_APPLY_DOT_SOURCE_READY + BACKFILL_DRYRUN_PROVEN (137 expected) + SAFE_APPLY_DECISION_MADE (leave ACTION_READY pending T2+permit).
Key numbers (live 2026-06-06)
| Item | Value |
|---|---|
| BIRTH_REQUIRED | 74 |
| Identity resolvable (after classify) | 70 (33 synthetic_id + 34 column + 3 legacy) |
| Identity unclassified remaining | 4 (no-id, needs-owner) |
| No-table REQUIRED | 2 (iu_staging_payload, iu_staging_record) |
| Dry-run eligible collections | 39 |
| Collections with non-zero delta | 5 (all governed) |
| Total expected new births (full QT-001) | 137 |
| Real backfill committed | 0 |
| birth_registry | 1,210,868 (macro net births = 0) |
| tga / apr | 129 / 42 (unchanged) |
The 5 backfill targets (all governed, zero duplicate risk)
dot_domain_rules 67 · apr_approvals 42 · normative_relations 18 · apr_action_types 6 · field_type_equivalences 4 = 137.
Read order
01 stage1-reverify · 02 identity-classification · 03 metadata-repair · 04 required-preflight · 05 plan-DOT · 06 apply-DOT · 07 full-dryrun · 08 controlled-apply-decision · 09 cross-layer · 10 design-index-update · 11 safety-audit · 12 final-summary · 13 checkpoint.
Artifacts on VPS
/opt/incomex/docs/mcp-writes/birth-stage2-2026-06-06/ — 01_classify.sql, 02_views.sql, 02b_fix_guard_aliases.sql, 03_apply_rehearsal.sql, 04_dot_birth_qt001_plan_SOURCE.sql, 05_dot_birth_qt001_apply_SOURCE.sql, 10_dryrun_numbers.sql, 99_rollback_stage2.sql.
Old dot-birth-backfill and dot-birth-trigger-setup remain FROZEN. No new apply-capable function was deployed live; the apply DOT is source-only pending T2.