On agent benchmarks the share of tasks that at least one run solves sits 10 to 32 points above the best single run, and only a selector with an external check can reach it. This draft asks what an imperfect check collects: a formula with two error rates per task, one released verifier, and two pre-registered runs of our own on the same 1,600 candidates. Model judges' false-reject rate, not their false-accept rate, rises with task difficulty; model-written tests, even after reading the code, accept 46% of the wrong patches. The rule with the largest point estimate, found after the pre-registered endpoints, gates on tests and ranks by a judge: 0.28 of the prize at eight candidates, with an interval that overlaps the tests alone.
The frame. On agent benchmarks the oracle, the share of tasks that at least one run solves, sits 10 to 32 points above the best single run (9.8 among the top seven SWE-bench Verified submissions, 19 to 32 in mid-ranked bands, 14 to 25 on τ-bench), and only a selector that checks candidates against something outside the solvers can reach it. A rule's share of the prize is (its accuracy − a random candidate) / (oracle − random) at the same number of candidates n. The draft replaces the single verifier error rate of the earlier working paper by two rates per task: false accept αi and false reject βi.
The formalism: three consequences.
A released model verifier (R2E-Gym, 500 SWE-bench Verified bugs, 12,695 candidates): the formula holds per task.
Our own verifiers on the same 1,600 Qwen3-Coder candidates (200 contested SWE-rebench issues, 8 rollouts each, prize 42.4 points; two pre-registered runs).
Independence of families: moves hundredths. On the SWE-bench Verified leaderboard (91 submissions with a known family), the residual error correlation after one difficulty factor is at most 0.09 within a family (Qwen +0.092) and −0.03 to +0.03 between families, against raw correlations of 0.4–0.5 from difficulty alone. Choosing a verifier from another family moves little; the false-accept rate decides.
In one sentence. A verifier's two error rates, measured per task, predict what a selector collects; on agent tasks the prize goes to a verifier with a small false-accept rate, and neither model judges nor model-written tests, blind or reading the code, supply one, so the best deployable rule found collects 0.28 of the prize at eight candidates by gating on tests and ranking by a judge.
The PDF (31 pages, 30 references) is on Zenodo: doi:10.5281/zenodo.23336060. Version 10 of 13 October 2026: the terms, the prior results, the formalism with its derivations, the six hypotheses with their pre-registered thresholds and verdicts, every experiment (E1 to E5b), a results section by question, and the conclusion. Sections 0–4 are the plan before the experiments, 5–6 the hypotheses and plan with verdicts, 7–9 and the Conclusion the results. A changed text gets a new Zenodo version.
Data: R2E-Gym, Jain, Singh, Shetty, Zheng, Sen and Stoica, R2E-Gym: Procedural Environments and Hybrid Verifiers for Scaling Open-Weights SWE Agents, arXiv:2504.07164, release R2E-Gym/32B_predictions on Hugging Face; Nebius, nebius/SWE-rebench-openhands-trajectories (CC-BY-4.0) and the swerebench environment images; the SWE-bench Verified leaderboard matrix and item-response fit of Agents with Tools Fail Together. Theory: Dorner, Chen, Cruz and Yang, ROC-n-reroll, arXiv:2507.12399; Stroebl, Kapoor and Narayanan, arXiv:2411.17501. Compute: 4,000 cloud sandboxes, under $10 in all.
The draft supplements the working paper Exploring the Boundaries of Multi-Agent Ensembles (doi:10.5281/zenodo.23311676), whose bound for a selector assumed a verifier with one error rate, and builds on these notes:
This is a working draft, not peer reviewed. The two runs of our own were pre-registered in full; of their five primary endpoints the two about tests being strict failed, two were undecided, and the per-task-rate endpoint held; the gate-then-rank rule was not among them. The R2E analysis was partly pre-registered, after a first look at the same data. Known limits: two benchmarks and two solvers, one verifier per kind, one test-writing model with at most five tests per issue; the 200 issues are contested by construction, so shares are shares on contested issues (29% of issues with eight candidates); per-task rates rest on about 13 candidates per half on R2E and 4 on our runs; "correct" means "passes the benchmark's hidden tests". Two data sets could not be used (the LLM-as-a-Verifier release ships no judge scores; the W&B Programmer submission stores only the submitted patch). The code and pre-registrations (sim_select.py, the E1/E3 analyses, the E5/E5b runs with PREREG.md, run.sh and verbatim model outputs, the family-residual matrices) are to be released as a companion repository. The verifier the formula asks for, one with a small false-accept rate that does not use the hidden tests, is still to be found.
Latipov, A. (2026). Paper Draft. What an Unreliable Verifier Collects (v10). Zenodo. https://doi.org/10.5281/zenodo.23336060. Archived with a DOI on 13 October 2026.