Skip to content

Move-Countermove Playbook

Reference playbook — instantiates Adaptive Opponent Rehearsal

A durable, living reference that maps the opponent's likely moves to your pre-worked counters and their counters-to-your-counter, distilled from rehearsals so the interaction can be prepared rather than improvised.

The Move-Countermove Playbook is the family's durable artifact: not an event you run once but a living document that captures, in advance, the opponent's plausible moves, your best response to each, and the opponent's likely response to that — a branching map of the interaction, held in a form you can carry into the real moment. Its defining move is that it persists and accumulates: where a wargame is spent when the session ends, the playbook is the sediment those sessions leave behind, refined move by move as new rehearsals and real encounters teach what actually works. It exists so that when the opponent makes the move, the counter is already reasoned, chosen, and rehearsed — the interaction prepared rather than invented under pressure.

Example

A college football team's coaching staff keeps a playbook for third-and-short against a specific division rival known for an aggressive run-blitz. It is organized as a tree. If the defense shows the A-gap blitz look → run the counter-trap that uses their aggression against them. If they then adjust to sit in the gap → the play-action off the same formation, because the linebackers have been burned by the trap and will bite. If they drop into coverage instead → the quick out to the flat. Each branch was not guessed; it was worked out in film study and walk-through reps, and each carries a note on the assumption it rests on — "assumes their mike linebacker keys the guard, which he did in weeks 1–4."

During the game, when the rival shows exactly that blitz look on third-and-two, the quarterback and coordinator are not improvising; they run the pre-worked counter, and when the defense adjusts the next series, they already have the branch for it. After the game, the staff updates the playbook: the mike linebacker had started keying the back instead, so the assumption note is revised and one branch is re-worked. The artifact is never finished; each encounter feeds it.

How it works

  • Build the tree from rehearsal. Distill wargames, film, and past encounters into opponent-move → your-counter → their-counter branches, not a flat list of tactics.
  • Attach the assumption to each branch. Record what each counter depends on — a tendency, a constraint, a read — so a branch can be invalidated when its assumption stops holding.
  • Keep it living. Treat every new rehearsal and real encounter as an update: branches get added, pruned, and re-worked as evidence accumulates.
  • Make it fast to use. Organize by the opponent's observable trigger so the right branch is findable in the moment the move appears, not after.

Tuning parameters

  • Branch depth — how many moves ahead the tree runs. Deeper trees prepare more of the interaction but grow unwieldy and rest on longer chains of assumption; shallow trees stay usable but get out-adapted sooner.
  • Breadth vs. focus — cover every opponent move or only the high-frequency ones. Broad playbooks are comprehensive but heavy; focused ones are sharp but blind outside their range.
  • Update cadence — how often the playbook is revised against new evidence. Frequent updates keep it current but cost effort and can churn; rare updates ossify into a stale script.
  • Assumption-tagging rigor — how strictly each branch names its dependency. Strict tagging makes stale branches easy to spot; loose tagging leaves the playbook confidently wrong when a tendency shifts.

When it helps, and when it misleads

Its strength is that it converts rehearsal into retained, reusable readiness: the reasoning done once in a wargame is captured so it can be executed fast when it counts, and because every branch is a small pre-formed "if their move, then my response," it functions as a set of implementation intentions for a contest[n1] — decisions pre-made so they don't have to be improvised under pressure.

Its failure mode is overfitting to a stale opponent: a playbook encodes the opponent as they were, and an adaptive adversary who notices the pattern will bait the branch and punish it — the very predictability that makes the playbook fast makes it exploitable. The classic misuse is running the playbook as gospel, executing the pre-worked counter after the opponent has already changed the tendency it assumed. The guarding discipline is to keep the assumption tags visible and to treat the playbook as a hypothesis re-tested each encounter, pruning any branch whose assumption the last game or last real move disproved.

How it implements the components

  • action_reaction_branching_map — its signature: the playbook is the branching map of opponent move, your counter, and their counter-to-your-counter, held in durable form.
  • assumption_exposure_surface — every branch carries the assumption it rests on, so the playbook doubles as a standing register of what the plan is betting on.
  • learning_capture_and_plan_revision — the living-document discipline is exactly the capture-and-revise loop: each rehearsal and real encounter updates the tree.

The playbook is an artifact, not an event: it runs no turn_structure_and_move_ledger live session and stands up no adaptive_opponent_model that reacts in the room — those belong to Tabletop Wargame, which produces the branches this playbook stores; and it does not score reversibility on a scoring_and_regret_matrix, which is Escalation Ladder Exercise.

Editorial Notes

Form Classification

Form family: Representation, Specification & Plan

Rationale: Move-Countermove Playbook operates as a non-executable information artifact that externalizes static or prospective structure because it a durable, living reference that maps the opponent's likely moves to your pre-worked counters and their counters-to-your-counter, distilled from rehearsals so the interaction can be prepared rather than improvised.

Independent corroboration: The frozen evidence defines Move-Countermove Playbook as 'A durable, living reference that maps the opponent's likely moves to your pre-worked counters and their counters-to-your-counter, distilled from rehearsals so the interaction can be prepared rather than improvised', so its operative form is Representation, Specification & Plan.

Review outcome: Independent reviewer agreement; high confidence.

Origin Attribution

Primary origin: Military & Strategic Studies

Origin pattern: Convergent development

Present-day reach: Multi-domain

Rationale: Preplanned branches for likely opponent actions and counters are rooted in military planning, wargaming, and tactical doctrine.

Related originating lineages:

Review resolution: Both independent reviews agree on primary origin military_strategic_studies; reconciliation resolves secondary fields (alternate_origin_disagreement, origin_mode_disagreement). Alternate origins retained (organizational_management, security_intelligence, psychology) are the union of reviewer-supported formative lineages with explicit rationales, not a list of later application domains. Present-day breadth is represented separately as domain_reach=multi_domain; origin_mode=convergent records the historical relationship among lineages. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=false preserves either reviewer's finding that the encyclopedia generalized the mechanism.

Review outcome: Reconciled after independent review; high confidence.

Notes

[n1] Implementation intentions, studied by the psychologist Peter Gollwitzer, are "if situation X, then response Y" plans made in advance; pre-forming the response makes it far more likely to be executed when the cue appears. A move-countermove playbook is a contest-scale version: each branch is a pre-made if-then that removes improvisation from the moment.