A six-hour review loop only matters if the evidence survives publication

Lustro's rapid-response plan uses a disinformation-cluster feed reviewed every six hours. High-risk cases are recalibrated right away. The engineering problem is what happens between that review and a social post.

A correction can arrive on time and still fail. Source links can disappear. Its reasoning can become impossible to check. Or the draft can repeat the unverified claim it was meant to address. A character limit does not excuse any of that.

I found Lustro through research published by ProjektLustro.eu. Jakub Sikora's whitepaper, "Cross-Lingual Information Diffusion and Temporal Alignment: Russian State Media and Polish Outlets", provides the research context. The rapid-response process described here is a program plan, not a claim that results have already been measured.

Treat drafts as evidence handoffs

For each cluster, the plan calls for a documented choice based on harm, audience, evidence quality, and spread potential. The response may be a correction, a prebunk, or restrained satire. The decision log should include that choice and preserved source links.

Different readers need this for the same basic reason. Researchers need to inspect the evidence and the decision. Journalists need an attributable correction they can verify before using it. People who see the post need a clear explanation that does not make them read the unverified claim again.

The line is clear. Lustro is not an automated verdict engine or a political persuasion campaign. It should not publish a claim-specific item if it cannot preserve the sources and decision log.

A reproducible pre-publication checklist

For a channel-native draft, I would check these points before publishing:

• Trace the input. Does the draft refer to a cluster from the Lustro feed rather than an unsourced social post?
• Record the decision. Are harm, intended audience, evidence quality, spread potential, and the selected response type documented?
• Keep the evidence reachable. Are source links preserved, and can readers find the matching decision log?
• Check for amplification. Does the draft repeat or materially amplify an unverified claim? If so, pause it. A prebunk can describe observable manipulation patterns without naming a live rumor.
• Validate the channel version. Does the draft meet the platform's length and other publication requirements without dropping the evidence trail or changing its meaning?
• Check the format's history. If removals, locks, or rule conflicts keep happening and moderator-approved adaptation cannot fix them, stop using that format.

This is a draft-review method, not a claim about an existing software pipeline. It makes failure states visible. "We had a source somewhere" is not source preservation. "We discussed it" is not a decision log.

What would count as evidence that it works?

The plan calls for counting approved responses with complete source links and decision logs. It calls for tracking high-risk review and recalibration against the six-hour cadence, and assessing documented changes in the reach and credibility of organized disinformation. It also counts verified volunteer signups, not incomplete submissions.

Those are evaluation targets, not reported results. The open methodological questions matter: how are reach and credibility assessed? How are decisions audited when a draft is paused? Public-interest responses need to be inspectable, not merely fast.

The project site and volunteer pathway are at https://projektlustro.eu.