KB-9CD3
10 — Final Routing & Patch Decision
2 min read Revision 1
birth-registryrouting2026-06-05
10 — Final Routing & Patch Decision
Router — v_birth_explosion_next_macro_router_v2
Inputs: runaway_state = NO_ACTIVE_RUNAWAY; h11a = CONTAINED; H11a no-go guard 3/3; gateway no-go guard 3/3. Output: BIRTH_TRIGGER_RECONCILIATION_MIGRATION — apply staged E (after 13:00-cycle verification), then RP_OBJECT_HYGIENE_UI_UPDATE_AND_FINAL_ACCEPTANCE.
Decision table walked
- Active runaway? No → not EMERGENCY_CONTAINMENT.
- Containment applied + policy patch ready? Yes (B/C/D applied) → not WAIT.
- Trigger contradictions remain? Yes (29 exempt + 18 dup + 50 deferred + 5 missing, all staged) → BIRTH_TRIGGER_RECONCILIATION_MIGRATION.
- All fixed? Not yet (E staged, RP UI not repointed) → reconciliation precedes hygiene UI.
Patch execution decision
- APPLIED now: B (config), C (fn_log_issue), D (fn_birth_registry_auto) — all reversible, rehearsed, birth-neutral, fail-closed. Within principal-delegate authority ("narrowly scoped config containment" + "policy enforcement after rehearsal and rollback proof").
- STAGED for operator/migration authority: E trigger DROPs, DEFERRED reclassification, optional partial unique index, RP UI repoint.
Next macro
BIRTH_TRIGGER_RECONCILIATION_MIGRATION → then RP_OBJECT_HYGIENE_UI_UPDATE_AND_FINAL_ACCEPTANCE. Fallback WAIT_WITH_BIRTH_WATCH only if the 13:00 cycle shows regression.