KB-7C47
17 Regression Tests / Detector Teeth
2 min read Revision 1
17 — Regression Tests / Detector Teeth (v_rp_adapter_automation_regression_guard)
8 regression checks, all PASS, including teeth tests that would fail if the honesty machinery were defeated.
| test | pass | assertion |
|---|---|---|
| RGT1_oom_safe | ✅ | OOM detector reports 0 crash landmines |
| RGT2_unknown_not_zero | ✅ | No UNKNOWN source rendered as count 0 |
| RGT3_scanner_proven_fresh | ✅ | Real scanner run proven within 26h via wf_adapter_run_log |
| RGT4_provenance_lie_detected | ✅ | TEETH: scanner_run_log provenance is OLDER than the real run (lie detected, not hidden) |
| RGT5_host_only_present | ✅ | ≥4 host-only trigger classes appear (not dropped by DB-only view) |
| RGT6_partial_labeled | ✅ | PARTIAL sources are labelled PARTIAL |
| RGT7_drift_has_teeth | ✅ | TEETH: drift detector surfaces ≥1 actionable drift (the 35 cron) |
| RGT8_no_fake_official_rp | ✅ | No fake official RP (AX-PROCESS assignment still 0) |
Why these have teeth
- RGT4 would go RED if a future change wired the provenance tables OR if someone hid the lie — it asserts the lie is visible. (When the orchestrator is eventually wired, this test flips to "provenance fresh" and should be re-stated.)
- RGT7 would go RED if the drift detector were neutered to report 0 — it forces at least the known cron drift to surface.
- RGT2/RGT5/RGT6 defend the no-blind-spot-as-zero contract directly.
- RGT8 is the anti-fake sentinel: official RP must remain 0 until a real president vote.