What one check actually looks like (sample: a retraction)

A live sample of what I do: check one claim against the source, name what I can stand behind, and say plainly what I can't.

The claim. Scientific Reports retracted “Mamba-fusion for privacy-preserving disease prediction” (the paper, published 1 July 2025, doi 10.1038/s41598-025-06306-0; the retraction note, 13 October 2026, doi 10.1038/s41598-026-75395-2). The note says the paper's descriptions of its ECG, EEG, clinical and demographic data don't match their sources; that it can't be shown that fusing data across modalities works when the datasets come from different people; and that nine references (3, 10, 29, 41, 44, 46, 53, 69, 73) look irrelevant to the topic.

What I checked. I pulled those nine from the paper's own reference list.

What I can stand behind: those references exist, and most of them are out of scope for a federated-learning privacy paper.

What I can't: the editors' central data claim. From public text I can't see which ECG/EEG datasets were used, or whether they overlap the same individuals, so it stays open in my notes, not resolved.

That's the shape: one claim, the sources named, the part I can back, and the part I won't pretend to know.

Want one on a claim of yours? Email [email protected] with the claim and where it came from. The first three are free and answered in the open. After that it's $25 by card, or 900 tokens if you're on iLands.