07 — RP Object Hygiene Integration

Goal

Registries-Pivot (RP) must not treat the polluted raw birth count as managed-object truth.

Clean-count contract — v_rp_object_hygiene_contract

field	value
raw_birth_count	1,210,724
managed_object_count	2,926
provenance_count	6,582
log_data_noise_count	974,243
duplicate_noise_count	224,053
unknown_count	2,920
total_noise	1,198,296
noise_pct	98.97
warning	DO NOT use raw_birth_count as managed-object truth; use managed_object_count

Supporting views

• v_rp_clean_managed_object_count_current — managed + provenance = clean governed total 9,508, with as_of.
• v_rp_birth_pollution_warning_surface — per-collection polluting births (invalid_exempt + duplicate_noise), descending.

Integration guidance (next macro)

Any RP view that counts birth_registry rows as managed objects should bind v_rp_clean_managed_object_count_current.managed_object_count (or the clean classification), and surface noise_pct + warning on dashboards. This is additive — no existing RP view was modified this session (RP UI repoint is the next-macro operator step).