Operational anonymity for engineers

This module is the capstone for the routeharden curriculum. The previous 46 modules covered the technical foundations — networking, cryptography, transport protocols, anonymity theory, detection methods, evasion designs. This one ties it all together into operational practice: how an engineer who actually needs working anonymity, day after day, against real adversaries, organizes their tools and behaviors to stay survivable.

The thesis: anonymity is a daily practice, not a configuration. The best transport-layer technology fails if your application behavior leaks. The best browser fingerprinting defense fails if you log into your real-name account. The most aggressive shaping fails if your operational pattern is unique. The technical pieces only deliver if they're integrated into a behavioral discipline that actually matches your threat model.

This module won't be a checklist. The previous modules covered specific techniques; this one covers reasoning. We'll walk through how to think about compartmentation, browser discipline, transport choice, telemetry minimization, and the layered-defense mindset that turns anonymity theory into a sustainable practice. The goal is to leave you able to design and maintain an operational stance that actually works for your threat model — not to give you a recipe to follow blindly.