The developer toolchain, for the time of AI.
Wiener Gate: public evidence corpus
An evidence-bound investigation into a multi-brand online pet-purchase fraud network, documented as a criminal supply chain rather than a single suspect.
Read the brief written for you
For law enforcement
Who, what, when and where, with the infrastructure findings laid out for a referral.
If you have been targeted
What to do now, how to file with IC3, and how to tell a fake listing from a real one.
For technical analysts
Procedures, tooling and indicators, written so you can reproduce the findings yourself.
Analytic assessment
Hypotheses with confidence levels, a devil's advocate pass, and what would disprove us.
How to help
Passive observation, safe reconnaissance, and how to reach victims without harming them.
The master brief
Every brief and the full wiki reference layer compiled into one document.
The rest of the corpus
These are markdown, and live in the repository rather than on this site.
- The wiki: network map, domain roster, indicators, methodology, glossary and changelog.
- Verify our work: what each hash manifest covers, and how to check an artifact against it.
- The redaction contract: the rules this corpus holds itself to, published so you can audit them.
- The repository itself, including every brief in markdown.
How to read this
- This is an evolving situation. Findings marked
PROVISIONAL,UNVERIFIEDorHYPOTHESISmay change. - Every load-bearing claim carries a pointer to the section of the private evidence log supporting it, in the form
(Z-7),(U-4),(R-1). - The evidence tree does not ship. It holds victim identities, suspect-side financial detail, and images belonging to people who never consented. That exclusion is deliberate and the boundary is written down in the redaction contract.
- Found an error? That is the point. Corrections are recorded with the same care as findings.