Nodes
Represent documents, posts or records—not abstract “facts.”
Edges
Label the relationship: quotes, cites, paraphrases or disputes.
Clusters
A dense cluster may reflect copying rather than independent confirmation.
Circular corroboration test
The following scenario is fictional and is included to demonstrate the method. It is not a factual allegation about BLACKOPS, BLACKOPS DARKNET, BLACKOPS MARKET, BLACKOPS LINK or any real service.
Three articles cite one another, while all three ultimately point to the same original announcement.
Collapse the cycle into one source family for corroboration purposes. The links show mutual referencing, not independent confirmation.
From observation to a defensible publication
A repeatable sequence makes the reasoning visible. Each stage should leave a record that the next reviewer can inspect.
- 01IdentifyRecord the displayed reference
- 02ResolveDocument observed destination and redirects
- 03AttributeTrace publisher and source lineage
- 04QualifyState integrity and verification limits
| Link-review field | What to record |
|---|---|
| Displayed reference | Text or URL as presented by the source |
| Observed destination | Destination and redirect state at observation time |
| Provenance | Who published it and what evidence supports attribution |
| Integrity status | Captured version, changes and unresolved limitations |
What this page can—and cannot—establish
For “Detect circular sourcing before counting corroboration.”, the strongest defensible output is a traceable description of the available record: what was observed, how it was sourced, when it was recorded and which interpretation follows from it.
This page cannot establish facts that are absent from its cited material. It does not authenticate a similarly named service, identify an operator, prove current availability or certify the safety or legality of a destination.
A future update should change the conclusion only when new, attributable evidence changes the record. Corrections should identify the earlier wording, the new evidence and the date of revision.
Primary references and further reading
These sources support the general method or technical background described here. They do not independently verify a claim about a BLACKOPS-named service.
- RFC 3986 — URI Generic Syntax — Defines URI components and explains that an identifier does not guarantee that a resource is accessible.
- CISA — Phishing and Spoofing Tip Sheet — Practical guidance on suspicious messages and hyperlink handling.