KB-5E97

05 — Object Truth & RP Managed-Count Control

2 min read Revision 1

Supertrack E — Object Truth & RP Managed-Count Control

Live decomposition (fully accounted, not hidden)

bucket count
raw_birth_count 1,210,783
managed_object_count (SSOT) 2,929
provenance_count 6,610
log_data_noise 974,243
duplicate_noise 224,075
unknown 2,926
total noise 1,198,318 (98.97%)

The five buckets sum exactly to raw (2,929 + 6,610 + 974,243 + 224,075 + 2,926 = 1,210,783) — the "unknown" residual is accounted, not concealed. The hygiene contract warning reads: "DO NOT use raw_birth_count as managed-object truth; use managed_object_count."

RP surfaces referencing raw births

Of the 8 RP views that reference birth_registry, exactly one has repoint_recommended=true (v_rp_authority_execution_preflight, classed RAW_COUNT_DIAGNOSTIC_FACT), and even that is an operator-UI conditional repoint — "no DB SSOT change required (truth contract already clean)." The other 7 are intentional, labeled simulators / regression-guards / live-size watches. No RP SSOT view uses raw births as object truth; pollution is not hidden, raw diagnostic visibility is preserved.

Guards

  • v_rp_raw_vs_clean_count_guard (single heavy scan): managed_distinct_from_raw ✓, no_hidden_births_all_accounted ✓, managed_is_small_clean_subset ✓, raw_diagnostic_still_visible ✓.
  • v_rp_count_semantics_regression_guard (lightweight, pollable): 5/5 pass — no DB SSOT view requires a raw repoint; ≤1 operator-UI repoint outstanding; managed SSOT column present; raw diagnostic view present; object-truth control plane published.

No DB-side repoint was needed or applied. The only outstanding item is an optional operator-UI change (forbidden to deploy here).

Views built: v_rp_object_truth_control_plane, v_rp_raw_vs_clean_count_guard, v_rp_count_semantics_regression_guard.

Back to Knowledge Hub knowledge/dev/reports/architecture/authority-birth-truth-control-plane-p0-remediation-2026-06-06/05-object-truth-rp-managed-count.md