Skip to content
Preprint

Prior Audit-Repair Context Shifts LLM Verifier Thresholds Toward Leniency

Aug 2026 · 0 citations · 22 references
Computer Science

TL;DR

Measuring false alarms on human-verified-correct ProcessBench traces with the present task held byte-identical, it is found that a completed audit ->repair episode already in the model's context lowers false alarms in 15 of 15 model x wording combinations.

Abstract

Automated checking pipelines increasingly place one language model as the checker and another (or the same one) as the fixer. We ask whether that wiring changes what the checker reports. Measuring false alarms on human-verified-correct ProcessBench traces with the present task held byte-identical, we find that a completed audit ->repair episode already in the model's context lowers false alarms in 15 of 15 model x wording combinations, by 2.8 to 11.5 percentage points against a length-matched non-audit control, a 9 to 25% reduction relative to that control. The direction contradicts what the accumulated-message literature predicts: an episode whose audit reported an error lowers false alarms further still, at all five wordings on the model where that manipulation lands cleanly, though a negativity asymmetry predicts more flagging. Decomposing the episode finds repair content and audit verdict complementary: different components carry the effect on different model families. Signal-detection analysis locates the change in the threshold rather than in discrimination -- the criterion moves in 15 of 15 combinations and survives correction in 13 while d'survives in none, though the d'test is half as sensitive by construction -- and a hand audit of 50 false alarms finds 82% simply wrong, so at this operating point the shift need not be harmful. With reasoning enabled the effect keeps its relative size on both models tested, and the threshold reading holds there too.

View source

Similar papers

Open access Aug 2026

Three Measurement Hazards in Analyzer-in-the-Loop Repair of Smart Contracts

An executed exploit is reported showing a specification-level authorization defect that produced no high or medium impact finding, its consequence for repair metrics, where it biases both transition counts upward and can confound comparison between methods producing differently sized .patches.

Staley Ian · 0 citations
Preprint Aug 2026

Auditable Release Control for Pedagogical Leakage in LLM Tutors

These results establish an auditable release boundary and failure attribution under declared contracts, not universal semantic safety or learning gains, not universal semantic safety or learning gains.

Nizam Kadir · 0 citations
Jul 2026

Validation Evidence in LLM Repair Agents: How Much of What Passes Actually Tests the Bug?

When a repair agent runs a test and sees it pass, the result is treated as evidence about the reported defect. We measure how often that treatment is warranted. BSG-VA (buggy-state/candidate-state/gold-fix validation analysis) captures each validation command at its exact working-tree state, extracts a test-only patch,...

Xiaonan Xu, Wenjing Wu · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.