Before / after
Why the original verdict was incorrect
The driver scored rougeL (sentence-level longest common subsequence) and compared it against the paper's Table 3 R-L of 40.90, which is in fact rougeLsum (summary-level longest common subsequence per Lin 2004). The two metrics measure different things. Under the correct metric variant the model lands within paper bounds.
Evidence trail
- Audit thread — long-form post-mortem covering all seven 2026-05-13 retractions, including this one.
- Rollback PR — the GitHub pull request that landed the corrected driver and flipped the verdict row to
is_current=false. - All public retractions — the append-only retraction log under PRD §17.X.8(d).
- Verdict Validator — the C1/C2 gates that prevent this class of mistake from shipping again.
What changed structurally
The 2026-05-13 retraction rollup landed two structural fixes so the citation-side failure that caused the original incorrect verdict cannot ship the same way again:
- Typed claim citation per verdict. Every reproduction driver now declares a structured
CLAIM_CITATION(Table, row, column, reported value, quoted text, PDF page) before its Modal job runs. The original verdict on this paper was published against a non-citable headline — that path is now closed by the build-failing validator-wiring lint. - PDF-verified textual gate. The Verdict Validator fetches the cited paper's PDF and checks that the quoted text appears within ±200 characters of the cited reported value. Made-up, mis-cited, or category-confused citations fail this gate and the verdict is auto-downgraded.