Author
Abstract
In machine learning a capability claim becomes established when a model outperforms its predecessors on benchmarks the community already accepts, and peer review confines itself to checking that those scores are reported and compared correctly. We argue that benchmarks consequently perform the adjudicating role that peer review performs in other sciences, and that the field has organised no stewardship to match, since a benchmark is reviewed once, when the paper introducing it is accepted, and never again during the years in which it serves as evidence. Our position is that this arrangement, which we call review once and use forever, is the first bottleneck a meta-science of AI research should address. We support the position with the public lifecycle of MMLU, the benchmark its successors describe as the de facto standard for general capability. Between 2024 and 2025 five independent projects repaired four distinct defects in MMLU, none of them by the original authors and none as part of any joint programme. A count across the benchmark paper, model reports, leaderboards and governance syntheses then shows the qualifications attached to an MMLU score falling from 2.4 per reporting event in the repair papers to 1.0 in frontier model reports, three in ten of which carry none. On this basis we propose three norms for venues, funders and governance bodies, and we answer the objection that unstewarded benchmarks have served the field well.
Suggested Citation
Zhu, Louis Yiven, 2026.
"Position: A Score Should Travel With Its Repair History,"
SocArXiv
7bg8r_v1, Center for Open Science.
Handle:
RePEc:osf:socarx:7bg8r_v1
DOI: 10.31235/osf.io/7bg8r_v1
Download full text from publisher
Corrections
All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:osf:socarx:7bg8r_v1. See general information about how to correct material in RePEc.
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
We have no bibliographic references for this item. You can help adding them by using this form .
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: OSF (email available below). General contact details of provider: https://socarxiv.org .
Please note that corrections may take a couple of weeks to filter through
the various RePEc services.