KB-219A
12 No-Blind-Spot-As-Zero Guard
2 min read Revision 1
12 — No-Blind-Spot-As-Zero Guard (v_rp_no_blind_spot_as_zero_guard)
The contract that the UI cannot silently render an unknown/partial/stale/host-only source as zero. 7 rules, all PASS.
| rule | pass | meaning |
|---|---|---|
| unknown_source_not_zero | ✅ | No UNKNOWN-scope source carries observed_count=0 (ui_route is NULL) |
| partial_source_badged | ✅ | Every PARTIAL source carries a PARTIAL UI badge |
| stale_source_warned | ✅ | Every STALE/STALE_PARTIAL source shows a warning |
| host_only_not_disappeared | ✅ | ≥4 host-only trigger classes remain in the universe |
| db_only_trigger_label_persists | ✅ | DB_ONLY trigger label persists |
| missing_adapter_raises | ✅ | No instrumented source is MISSING_ADAPTER |
| rp_visible_triggers_honest_zero | ✅ | Triggers report RP-visible=0 honestly (AX-TRIGGER unregistered) — a true zero, not a hidden one |
The key distinction
There are two kinds of zero. A hidden zero (a source that exists but renders as 0 because the view can't see it) is forbidden. An honest zero (RP-visible triggers = 0 because the axis is genuinely unregistered) is required and explained. This guard enforces the first and certifies the second. It is the gate the UI/operator pipeline checks before trusting any count.