Loading the interactive demo for "Three cases. Download. Investigate. Reveal."… The lesson text below is already here. The hands-on part loads next (requires JavaScript).
Three fictional investigations with real downloadable fixtures. Work each with the free tools, compare, audit, reason, then reveal the solution.
In order: triage, geometry, then the map. Each assumes the previous lesson.
How to work a case
Download the pair before reading further. Run the steps with the linked tools, write down your verdict, then reveal.
Wrong answers teach more than right ones here. Every mistake maps to a chapter that explains it.
Running it as a studio drill
Share the fixtures with your team or VA. Whoever closes all three without peeking owns leak response.
Time it: a practiced first hour beats a panicked one.
Takeaways
- Triage before attribution: compare, audit, then decide on Inspect.
- Cropping is deletion; collisions are inconclusive. Both have tells.
- Every case ends at the same place: fix the route for the next drop.
Check yourself
Optional, local, instant. 0/2 answered.
- Case 002's crop drops the verdict a tier. The lesson?
- After closing any case, what is the last step?
For your niche
Drill case 002 with your own cropped client exports: geometry lessons stick to your own files.
Case 003 is your highest-probability incident. If the team learns one case, make it that one.
Case 001's repost pattern matches art-theft accounts exactly. Practice the takedown pairing with chapter 12.