Birth Gateway SSOT + QT-001 Repair Design — Read Me First

Date: 2026-06-06
Status: PASS — implementation-specific design complete; no implementation performed

Current design documentation does not suffice. The repair establishes one birth control-plane: collection policy + identity metadata → shared PG policy/identity/register functions → thin realtime trigger + QT-001 procedure → paired DOT plan/apply + health scanner → RP active-object truth.

Core Decisions

• SSOT is an immutable versioned Git migration release plus runtime semantic contract/hash registry.
• dot-birth-trigger-setup becomes trigger reconcile only and can never redefine the gateway.
• Realtime and QT-001 share the same PG policy, identity resolver, and birth register function.
• QT-001 becomes one-collection plan/apply with exact preflight, batch transactions, exempt audit ledgers, and uncertified births.
• Deferred/exempt collections do not create direct managed births.
• QT-003/QT-003R hard-gate the first data row; >0 rows route QT-001.
• QT-006 is a separate universal lifecycle-state law/design program.

Live Conditions

global DOT preflight BLOCKED
birth admission permit absent
backfill ledgers absent
BIRTH_REQUIRED=74
required identity strategy unclassified=43
required without accepted birth trigger=5
required collections with native status=54/74

First implementation macro: BIRTH_P0_STAGE0_DANGEROUS_DOT_EXECUTION_FREEZE.