KB-42F3 rev 2

CHECKPOINT — Birth Registry Object Explosion / Log vs Managed Object Audit

2 min read Revision 2
checkpointauditbirth-registryPASS2026-06-05

CHECKPOINT — Birth Registry Object Explosion / Log vs Managed Object Audit

Final status: PASS
Mode: Live investigation READ ONLY; five Agent Data report uploads after proof
Verdict: BUG + ARCHITECTURE_GAP + DATA_NOISE

Exact 5,195 delta: entity_labels=4,043; system_issues=1,013; registry_changelog=121; knowledge_documents=18.

The 18 documents are legitimate report provenance. Remaining 5,177 rows came from the 10:00 UTC three-hour dot-hc-executor run: H11a detect-and-fix → heal_description_basic → 1,000 repeated issues with healed=0/anti_loop=1000 → labels → Directus flow changelog → fn_birth_registry_auto().

Proven defects: no semantic idempotency key; birth gateway ignores coverage policy; entity_labels and registry_changelog birth despite exempt policy; duplicate system_issues birth trigger; 78 production trigger-policy contradictions.

Impact: 33,326 births from explicitly exempt collections in 24h; H11a all-time 216,378 rows for 2,105 entity codes with 214,273 duplicates.

Audit end: birth_registry 1,210,686 → 1,210,699; 13 additional births, all knowledge_documents. After five required report uploads, final count was 1,210,704. Faulty ~5k spike did not continue during audit but remains scheduled.

Immediate recommendation: authority-gated pause of only H11a heal_description_basic or switch H11a to detect-only; no manual trigger mutation.

Back to Knowledge Hub knowledge/dev/reports/architecture/checkpoint-birth-registry-object-explosion-log-vs-managed-object-audit-2026-06-05.md