Countermove Rotation Playbook¶
Protocol — instantiates Cyclic Dominance Counterbalancing
A playbook that tells actors which counter-option to preserve, test, activate, or de-emphasize under specific observed conditions.
A Countermove Rotation Playbook is the conditional action document — a set of "if you observe X, then activate / preserve / test / de-emphasize option Y" rules — that turns a static beats-map into live play. Its defining move is that it binds each counter-option to an observable trigger and to a switch-cost gate: rotation happens because the environment did something specific and because the move is worth its cost, not on a fixed calendar and not on a hunch. The relation map tells you who beats whom; this playbook is the standing instruction for what to do about it the moment the field shifts.
Example¶
A security operations team defends against attackers who keep adapting. It runs three control families, each countering the adaptation that defeats another: signature detection (fast against known payloads), behavioral anomaly detection (catches novel payloads that evade signatures), and deception — honeypots and decoy credentials — which catches adversaries who have learned to blend into normal behavior. The playbook writes the rotation down. If you observe novel payloads slipping past signatures → raise behavioral detection to primary. If attackers start mimicking normal user behavior to evade anomaly scoring → shift weight to deception. If they begin mapping and avoiding the honeypots → refresh signatures for the now-known toolset. Each rule carries a switch-cost gate: retuning anomaly baselines takes about two weeks, so the playbook says never fully swap control families mid-incident — keep partial coverage and rotate the emphasis, not the whole stack. The result is that when a new intrusion pattern appears at 2 a.m., the on-call analyst reads the trigger and knows the counter, instead of improvising.
How it works¶
- Enumerate the triggers. For each edge of the cycle, name the observable signal that says the environment now favors a particular counter — drawn from the context vector, not from vibes.
- Bind trigger to countermove. Map each trigger to the option that beats the currently ascendant threat, and to the verb — preserve, test, activate, or de-emphasize — since not every shift calls for a full switch.
- Gate on switch cost and latency. Attach a cost/latency check to each activation: if the option takes longer to stand up than the window of advantage lasts, the rule is to pre-warm or partially cover rather than swap.
- Add hysteresis. Require the signal to persist past a threshold before rotating, so the team doesn't thrash on noise.
Tuning parameters¶
- Trigger sensitivity — how strong a signal must be before the rule fires. Twitchy triggers adapt fast but chase noise; sluggish ones are stable but slow to counter.
- Switch threshold — the cost/latency bar an activation must clear. A high bar prevents wasteful churn but can leave you stuck on a losing option too long.
- Rotation granularity — full swap versus a shift in emphasis. Emphasis-shifts are cheap and reversible; full swaps are decisive but expose you during the changeover.
- Observability of the rules — how transparent the playbook is to insiders (and adversaries). Transparency aids coordination and legitimacy but hands an opponent your reaction function.
- Hysteresis band — how long a trigger must hold before acting, trading responsiveness against flip-flopping.
When it helps, and when it misleads¶
Its strength is speed and legibility under pressure: the debate about "what do we do now" is settled in advance, so response time collapses and the counter is chosen by the field's behavior rather than by whoever is loudest in the room.
Its failure mode is that a fixed playbook is a published reaction function — an adaptive opponent who learns your triggers can act inside your loop, feeding you the exact signal that makes you rotate into the option they are now prepared to beat. This is the shadow side of Boyd's OODA loop: fast, predictable orientation is only an advantage until the adversary is orienting to you.[n1] The classic misuse is following the playbook so rigidly that it becomes exploitable, or letting it trigger on noise so the team churns options every week. The guarding discipline is to keep some unpredictability in the timing, hold rotations behind a hysteresis band, and periodically re-audit which triggers still track real advantage.
How it implements the components¶
rotation_or_mix_policy— the conditional if-then rules are the rotation policy in operational form: the executable statement of when each option is preserved, tested, activated, or de-emphasized.context_condition_vector— every rule keys off a named, observable condition, so the policy is driven by the environment's actual state rather than a schedule.switch_cost_and_latency_boundary— each activation is gated by the cost and stand-up latency of the move, so the playbook never orders a switch that can't complete inside its window of value.
It does not hold the relation data it reads — magnitudes live in Cyclic Payoff Table — and it does not watch for long-run drift or re-weight the mix; that standing revision is Adaptive Mix Review's job, and the minimum-representation floors are Portfolio Minimum-Viability Rule's.
Related¶
- Instantiates: Cyclic Dominance Counterbalancing — it is the operating layer that turns the counter-relation map into moment-to-moment play.
- Consumes: Cyclic Payoff Table — reads the pairwise relations to know which counter beats the ascendant threat.
- Sibling mechanisms: Beats-Relation Matrix · Cyclic Payoff Table · Portfolio Minimum-Viability Rule · Pairwise Dominance Audit · Adaptive Mix Review · Sentinel Option Trial · Nontransitive Scenario Simulation
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: The playbook binds observable conditions to preserve, test, activate, or de-emphasize actions with cost, latency, and hysteresis constraints, so its operative form is a standing conditional action rule.
Nearest alternative: Protocol, Workflow & Routine — Actors can enact its moves in sequence, but trigger-to-countermove mappings rather than one fixed ordered process define the playbook.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Military & Strategic Studies
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Strategic doctrine cohered conditional playbooks that bind observed opponent or environment states to preserved and activated countermoves.
Related originating lineages:
- Economics & Finance — Game theory supplies strategic response, cyclic dominance, and switching-cost reasoning among options.
- Organizational & Management Science — Contingency planning supplies observable triggers, owners, and standing if-then action rules.
Review resolution: Both reviewers identify military strategy as primary. Game theory and organizational contingency planning materially shape the condition-triggered rotation playbook, and the generalized nonmilitary formulation is synthetic and multi-domain.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] The OODA loop (Observe–Orient–Decide–Act), from military strategist John Boyd — the idea that whoever cycles through observation and response faster gains the initiative. Its corollary is the warning here: a fast but predictable loop lets an adversary anticipate your rotation and act inside it, which is why a rotation playbook must guard its own predictability. ↩