An adversary is the specific actor whose actions the threat model defends against. The Predaxia editorial discipline insists on naming the adversary specifically rather than abstractly: “the abusive ex-spouse who has access to the family Apple ID” rather than “stalkers”; “the prosecutor in the divorce case who will use forensic accountants” rather than “the legal system”; “the Russian intelligence service interest in NGO operations in Eastern Europe” rather than “nation-state actors.” The named adversary determines which countermeasures are operational and which are theatrical.
What it means in practice
The named-adversary discipline matters because countermeasures have costs and the wrong target wastes them. The user worried about “hackers” generically buys hardening tools that defend against credential phishing, while the actual adversary is the abusive ex-partner with the iCloud credentials who needs no phishing because they were given the credentials during the marriage. The user worried about “the government” buys VPN and encrypted messaging, while the actual adversary is the divorce lawyer’s forensic accountant who will subpoena bank records the VPN does not affect. Naming the adversary forces the operator to ask: what does this specific party want, what tools will they actually use, what defenses meaningfully cut their leverage? The Predaxia case-study format builds every protocol around the named adversary, which produces protocols that work because they target the actual threat.
Where it shows up
Required by every Predaxia Operator Protocol: the second section names the adversary specifically, with named individuals where applicable (ex-partner Sarah, divorce attorney Smith, the Russia-aligned threat group tracking the publication), named organizations where individuals are not the unit (the Iranian Revolutionary Guard cyber unit, the corporate-investigations function at the company being investigated), or named role-categories where specific identification is unavailable but the role is determinative (the unidentified Pegasus operator subscribing to the surveillance product against this target population). The Predaxia editorial frame: an Operator Protocol that names “hackers” or “stalkers” or “the government” is a protocol that has not done the work of identifying the actual threat, and the resulting countermeasures are likely to defend against threats that do not apply while leaving real threats unaddressed.
What you can change today
For your most sensitive ongoing situation, name the adversary explicitly. Write down: who specifically is the threat, what specifically do they want, what tools do they have, what leverage do they have, what would success look like for them. The exercise takes 20 minutes and produces clarity that abstract thinking does not. For the divorce client: the named adversary is usually the spouse plus the spouse’s lawyer plus their forensic accountant; the operational protocol differs significantly from “be private generally.” For the journalist: the named adversary is usually the named subject of the investigation plus their legal team plus any state services with interest in the topic; the protocol differs significantly from “use Signal.” The naming exercise is the precondition for protocol-quality countermeasure planning.