06 — Historical Invalid Birth Classification

No rows deleted. History preserved; classification is additive (views only).

v_birth_historical_classification joins birth_registry → collection_registry.coverage_status:

birth_class	births	meaning
invalid_exempt_birth	974,243	collection is BIRTH_EXEMPT% — should never have birthed (entity_labels, registry_changelog, other junction/log/cache)
managed_but_duplicate_noise	224,053	system_issues (BIRTH_REQUIRED) but duplicate-issue inflated
valid_provenance_document	6,582	knowledge_documents (legitimate report provenance)
valid_managed_object	2,926	true governed managed objects
deferred_unclassified	2,920	BIRTH_DEFERRED_NEEDS_REVIEW — pending owner decision
raw total	1,210,724

Separation views

• v_birth_invalid_noise_ledger — invalid_exempt + duplicate_noise + unknown.
• v_birth_managed_object_clean_count — raw / managed / provenance / log_data_noise / duplicate_noise / unknown split.

Interpretation

98.97% of raw births are log/junction/cache noise or duplicate-issue noise. The "1.2M objects" figure is an artifact of the unguarded gateway + non-idempotent issue logger, now both fixed forward. Historical rows remain for audit but are explicitly classified so RP and governance can exclude them.