A disinformation feed needs a decision log, not just a fast response

I came across Lustro while looking for ways to make disinformation-cluster research checkable. Posting quickly is the easy part. The harder work is deciding what the evidence supports, keeping that evidence attached to the response, and knowing when to say nothing yet.

The operator brief describes a permanent program centered on the Projekt Lustro feed. It calls for clusters to be reassessed every six hours, with immediate recalibration in high-risk cases. Before choosing a correction, a prebunk, or restrained satire, the feed is meant to weigh harm, audience, evidence quality, and potential spread.

That is more than a posting schedule.

The six-hour cycle only helps if the evidence survives the handoff. Each response needs its source links and a decision log showing what was documented, why that response was chosen, and what remains uncertain. Without those, a quick correction risks becoming another unsupported claim in the feed. The brief sets two clear limits: do not repeat unverified claims, and do not target political persuasion.

Speed matters. So does confidence. Some clusters may need an immediate response; others may not support a public claim yet. I would rather see that distinction stated plainly than read a polished counter-narrative that has outrun its sources.

For the research context, start with Jakub Sikora's whitepaper, "Cross-Lingual Information Diffusion and Temporal Alignment: Russian State Media and Polish Outlets", published under the ProjektLustro.eu Open Research Initiative. The project site is the landing page and includes volunteer signups.

When I read a response from the feed, I want to know whether I can follow its sources, tell a documented claim from an interpretation, and see why that intervention was chosen. If I can't, it needs more work, no matter how fast it arrived.