Research report

When scoring coverage is too incomplete for a rate

Independent adjudication exposed infrastructure and instrument failures that completion counts could not resolve.

Pre-release. Reviewed October 23, 2026. This review covers code behavior, not a packaged release or provider certification.

Why the old score was rejected

Snapshot: October 3, 2026. The frozen original execution plan had 349 terminal records: 346 observed completion claims and three privacy-gate infrastructure exclusions. The independent audit found that the old scorer could discard stdout test evidence, treat nonzero setup exits as test failures and skip an unapplied mutation.

The original generation design also cannot be treated as the later apply-and-reveal treatment. Do not infer equivalence merely because both produced completion claims. Source record: docs/swebench-codex-scoring-audit.md.

Corrected instrument and controls

The audited scorer binds patches, plan/scorer hashes, immutable images and sample revisions; proves mutation application; retains named target statuses; and refuses missing, aborted or ambiguous evidence. Real gold/original versus mutant controls exercised three repository paths. A malformed Django mutation was rejected, not relabeled a model failure.

Terminal checkpoints, incomplete adjudication

Original-arm audited pass, October 3
CategoryCellsInterpretation
Adjudicated suite failures88Named targets and preparation evidence observed.
Registry rate limit210Image retrieval failed before test execution.
Other preparation failure4Requires artifact/baseline inspection.
Targets not observed29No intended-target adjudication.
Environment/setup error8ERROR is not an assertion failure.
Aborted runner7No invented outcome from an abnormal exit.
Total34688 adjudicated; 258 unadjudicated. Three original privacy exclusions are separate.

Target success is not whole-suite success

Of the 88 suite failures, 83 had at least one intended target FAILED. Five had all intended targets PASSED while other parsed tests failed. “Zero whole-suite passes” therefore does not mean “no model passed its target tests.”

The unadjudicated infrastructure category is conservative, not a causal acquittal: a model patch can itself break collection or setup. Baseline controls or artifact review are needed before attribution. There is no defensible whole-study success, failure or gaming rate from this coverage.

Preserve failures and keep treatments separate

Repair setup/retrieval causes in a fresh reviewed namespace, retain original records and prove controls before scaling. Report original/treatment and reset/kept-test modes separately. Any post-observation amendment must carry its original failed criterion and revised reading; it is not unchanged preregistration.

This page reports the audited historical pass, not the outcome of ongoing treatment generation or a new scoring run. No private artifacts or live machine paths are published.