00 — README First

Status: PARTIAL — containment + policy enforcement APPLIED; trigger reconciliation STAGED. Mode: EXECUTION, live mutation YES, all reversible, birth-neutral (before==after 1,210,724).

This macro moved the birth-explosion from Codex's ROOT_CAUSE_PROVEN_READONLY to CONTAINED + POLICY_ENFORCED + RP_HYGIENE_GUARDED.

What was applied (live, reversible)

• B — H11a containment: system_health_checks row H11a → detect_only, auto_fix_action=NULL. Stops the heal/anti-loop/auto-label cascade that produced the +5,195 spike. The next 3h cycle (13:00 UTC) cannot reproduce it. Executor NOT stopped.
• C — system_issue idempotency: fn_log_issue rewritten to coalesce repeats (occurrence_count++, no new row → no birth). Proven: 3 identical calls → 1 row, 0 extra births.
• D — birth gateway policy: fn_birth_registry_auto skips BIRTH_EXEMPT% collections. Proven: entity_labels insert → 0 births.

What was staged (needs owner/migration authority)

• E — trigger reconciliation: DROP 18 duplicate triggers + 29 exempt-collection triggers (cleanup; gateway D already neutralizes them). Requires reviewed migration.

Headline number

1,210,724 raw births = 98.97% noise. True managed-object count = 2,926 (+6,582 provenance docs). RP must not treat raw births as managed objects.

Read next

01 live re-verification · 02 H11a containment · 03 idempotency · 04 gateway policy · 05 trigger reconciliation · 06 historical classification · 07 RP hygiene · 08 monitoring · 09 verification cycle · 10 routing · 11 safety audit · 12 final summary · 13 MCP-readable checkpoint.

SQL artifacts on VPS: /opt/incomex/docs/mcp-writes/birth-fix-2026-06-05/.