# One report, many reposts

By Andrew Proctor · Published September 11, 2026, updated September 14, 2026

I built my OSINT workflow to follow developing events without repeatedly reading the same report. Grouping related coverage helps, but the number of posts in a group cannot tell me how many independent accounts support its claims.

A report can spread through quotations, screenshots and rewritten summaries. Each post may add another place where the claim appears without adding another source for what happened.

## Keep the origin of the claim

My collection workflow retains references to the material it gathers. Those references matter when assessing whether two reports depend on the same original account. A different headline or publisher does not settle that question.

A separate account can add evidence, but it still needs examination. I want to know when its material was recorded and whether it describes the same event. A later publication date does not necessarily mean the material is newer.

## What grouping establishes

Grouping organizes related reports for a reader. It does not establish that a claim is true. A summary needs to preserve a disagreement or unresolved detail when the supporting material does not settle it.

The website shows a limited public feed with posts and available media from the last hour. Source references remain in the private workflow; the public view does not expose the full evidence record. Its collection boundary and demonstration labels should make that limitation clear.

Related work: [OSINT workflow](https://raidz.net/projects/osint/).

Further reading: [Verification Handbook: When Emergency News Breaks](https://datajournalism.com/read/handbook/verification-1/when-emergency-news-breaks/1-when-emergency-news-breaks).

Canonical HTML: [https://raidz.net/notes/repeated-reports-and-evidence/](https://raidz.net/notes/repeated-reports-and-evidence/)