# A viral claim is not an incident report

A claim that goes viral does not automatically validate the information presented in it. When the same claim surfaces across multiple online communities within a short period, people tend to combine two questions into one: Is the claim accurate? How is it being spread? While the latter question is important, it cannot answer the former.

Simply because an assertion is repeated does not make it documented, even if all posts lead back to a single screenshot. For developers, this scenario is not a contest to win but an incident to manage. Preserve the original materials. Distinguish observations from inferences. Document what would alter the assessment. Begin with an evidence ledger Before writing a rebuttal, condense the situation into five key elements: Assertion: Precisely what is being claimed?

Provenance: The origin of the cited evidence Provenance: Where did the cited evidence originate? Confidence: Which parts can be verified, and which remain uncertain? Distribution: Where and when the wording first appeared Distribution: Where and when the wording first appeared Disconfirmation: Evidence that would contradict or resolve the claim Disconfirmation: Evidence that would contradict or resolve the claim "Many accounts posted this" belongs in the Distribution section, not the Confidence section.

A screenshot without a traceable source goes under Provenance, with the gap clearly marked. This is not proof. The final entry is often the most valuable. If no one can identify the evidence that would settle the matter, the response might become just another assertion competing for attention. Treat the source chain like a dependency graph A post references an article.

The article cites an unnamed source. Ten other posts reference the article. This may appear as eleven pieces of support; however, it is one unverified attribution and ten references to it. Trace each citation back to the primary material. Note where the chain concludes. If a screenshot is cropped, inquire about the full document's contents.

If a quote is translated, keep the original and translation separate. If the primary source is unavailable, disclose this. While this does not prove the claim false, it informs readers why it remains unverified. Analyze spread without presuming a coordinator Investigate timestamps, repeated wording, and reposts across communities.

These can reveal how a claim traveled and whether seemingly separate posts depend on the same source. However, they cannot establish who directed the activity or the reason for sharing it. People may copy phrases for ordinary reasons. Keep distribution observations and attributed intent in separate columns. Choose the smallest response the evidence supports A factual correction should pinpoint the unsupported assertion and specify the evidence needed to resolve it.

"Be critical of what you read" does not provide readers with a test to apply. If posting the claim is unsafe, explain the pattern instead: anonymous attribution, selectively cropped images, or citations that all end at one unsupported source. This serves as a preemptive warning without granting the original assertion another clean distribution route.

Satire's role is narrower. It might expose a contradiction, but it fails if readers remember the false claim better than the evidence gap. Reassess before repeating Fast-moving cases require short review cycles. At each stage, assess potential harm, the likely audience, available evidence, and whether the claim's spread has changed.

A six-hour reassessment is a reasonable practice for a live response. It is not a mandate to publish every six hours. Terminating the review is more crucial than adhering to a posting schedule. If the claim cannot be described without magnifying a harmful falsehood, cease. If the planned wording lacks reliable documentation, cease.

If a moderator advises against the approach, revise or cease instead of persevering. The objective is not to amplify a competing narrative. Make the claim's evidence, gaps, and pathway through the network clear while readers have the opportunity to reconsider sharing it.