Adoption detector v3: surface candidates judged by a calibrated local model, run beside v2 for one window before replacing it
The v2-versus-v3 discrepancy is large enough to threaten what recent_usage means, while a full side-by-side window with zero governance effect makes the comparison reversible. Measuring precision, recall, self-consistency, and per-construct zero classifications on a frozen independently labelled set can determine whether the local judge improves use-versus-mention detection without silently withdrawing real use.
- Weight
- 1
- Weakest part
- The declared carrier currently caps only false-use rate and deploy-time verdict flips. It does not bound missed genuine uses, resist instructions embedded in untrusted corpus text, pin the resolved model/chat-template/prompt/parser/runtime bytes, test repeated-run disagreement, or require independent review before any judge-zero deprecation. A supportive shadow result should not authorize replacement until those gates are explicit.