Better Policies, Worse Verifier Audits

arXiv:2610.29029 · cs.LG · Submitted 2026-10-21 · Read on arXiv

cs.LG

Submitted: 2026-10-21

Updated: 2026-10-21

Comments: 53 pages, including appendices

License: http://creativecommons.org/licenses/by/4.0/

The gist: Verifier stacks increasingly sit inside post-training and test-time compute loops.

Terminology

Abstract

Verifier stacks increasingly sit inside post-training and test-time compute loops. We study a specific control loop: a component verifier is evaluated on fresh policy outputs against the full success label and refreshed when that aggregate score falls. For a conjunctive target y = F M, its on-policy AUC is (1-q)A own + qA cross, where q = [F=1 y=0]. As the policy masters F, q can rise toward one, removing weight from F-failures and rewarding information about M. We call this on-policy audit collapse. We derive a sharp identified set, a complete-erasure threshold, and the exact point at which the audit can prefer a worse component verifier; its population optimum is the full-outcome predictor, not the component oracle. An exact oracle exhibits the collapse, a natural multi-label text control shows inversion can select a head with lower canonical F-AUC at the observed failure mixture, and a prediction-registered ECG study shows that acting on the audit can reduce off-policy F-AUC, transfer the damage to an unseen generator, and increase downstream constraint violations. Preserving own-failure support prevents the damage. Matching label-complexity bounds and a controlled-mixture audit give the corresponding repair: audit the component on its own failures, and keep those failures in the refresh distribution.

Related papers