Who it is for
Model and agent evaluation teams, procurement reviewers, and platform vendors whose release gates currently rest on a single reported score.
Why now
This window produced direct measurements of non-transportability rather than warnings about it: one-try success diverged from twenty-try reliability in stateful workflows, live-runtime and frozen-holdout rankings of the same agent configurations agreed at Spearman 0.13, an audit found most eligible eval units cannot support deterministic claim inference at a pinned commit, and a corpus expansion produced 6-10 point answer churn invisible to aggregate accuracy. A year ago the question was whether an eval pipeline could be run at all; now the question is whether its output licenses the claim attached to it.
What would kill it
Evidence that a single published operating point, at a fixed commit and runtime, predicts production reliability and procurement outcomes well enough that claim-relative auditing is unnecessary overhead — for example a vendor contract settled on pass@1 alone that later matched observed field reliability.