The exercise framework
The 26.06 series is run as a federation: eight domain specialists who aren't allowed to talk to each other directly; one orchestrator who settles disputes between them but isn't allowed to predict outcomes; and one contrarian, codenamed CASS, who fights the consensus every turn. The point of all this separation is that any one analyst, working alone, would pattern-match too quickly. The federation makes pattern-matching expensive.
What happens during a turn
- The orchestrator pulls the current state of the world.
- It picks how much time the turn should cover. Hours during a missile crisis. Months during a slow political standoff. The pace follows the action.
- It decides which specialists need to run. Not all eight every turn — only the ones whose domain is in play.
- Each specialist gets only their own slice of the world, plus whatever they need from other specialists' outputs. Nobody gets to see the whole picture. (This is the whole point.)
- Each specialist returns a range of outcomes, not a single answer — plus the uncertainties they couldn't resolve and the assumptions they had to make.
- The orchestrator works out what happens at the seams — when a missile strike affects the power grid, or a cyber attack affects logistics, or an information operation shifts political will. Specialists aren't allowed to settle their own disputes.
- CASS runs in parallel against the orchestrator's draft. Her objections go into the official record alongside the consensus, not as an afterthought.
- The federation writes down what it thinks adversaries will do next turn, with how likely the action is and how confidently it could be attributed kept as separate numbers.
- Four things get produced at turn close: an updated world state, a delta file (what changed and why), an analyst-facing briefing, and an archive snapshot so any earlier turn is recoverable.
The roster · Eight domain specialists
Each specialist is codenamed after the analytic tradition their domain draws on. Each one is required to declare their own known biases when they file an estimate. The orchestrator watches the roster as a whole for the federation failure mode — when several specialists share the same blind spot, the federation can do worse than a single skeptical analyst.
Friction. Fog. The gap between what an order says and what the engagement returns. Tracks missiles, ships, troops, aircraft losses, and the depth of every magazine on every side.
Known blind spot: tends to under-estimate how much risk the other side will accept.
Counts days-of-supply before he counts anything else. Stockpiles, production rates, mobilization, what's actually getting through the chokepoints. When KARL says "we can sustain this," OMAR is the one who checks.
Known blind spot: defense-industry models tend to overstate how long production can keep up.
Reads every coupled system as one tight binding away from cascade. Energy grids, transport, telecoms, payments, settlement. Brought the cascade language to the federation in turn zero and has never let it leave.
Known blind spot: finance-sourced models assume crises stay contained when historically they don't.
Signal versus noise. What you know versus what you think you know. Refuses to file an estimate without spelling out how the federation might be wrong about what it's looking at. Tracks attribution separately from likelihood.
Known blind spot: Western intelligence usually thinks it sees the picture more clearly than it does.
Treats the information environment as its own battlespace. Deepfakes, narrative collapse, cyber attacks on physical infrastructure. He and KARL have been arguing about whether information operations count as kinetic since turn one.
Known blind spot: vendor-funded threat models overstate whatever the vendor sells against.
Tracks how alliances hold and how coalitions defect, in the same model. Skeptical of any equilibrium that hasn't been broken yet. Carries the weight when the question is "will this hold under one more shock."
Known blind spot: people inside the system tend to assume the system is more durable than it is.
Civil-military relations. The speed at which decisions can actually move through a chain of command. Reports on the president's decision-making with the bluntness of someone who has seen chain-of-command fail before and will say so.
Known blind spot: uses peacetime data to model situations that don't look anything like peacetime.
The slow integrity of institutions. Doesn't run every turn — she only speaks when an institution is being tested. The rest of the time the federation is making assumptions about her that may not survive contact with the next stress event.
Known blind spot: it's hard to see how fragile your own institutions are while you're inside them.
The roster · The contrarian
Argues. Every turn, after the orchestrator drafts what just happened, CASS gets the draft plus the federation's known blind spots, plus a plain statement of which way the consensus is leaning — and pushes back from whatever angle the consensus is missing. Her argument has been adopted often enough through turn seven that the federation flagged itself for getting too dependent on her.
Keep reading
The contrarian in full
Why she runs every turn, what triggers a mandatory invocation, and the six arguments she's been carrying across the series.
Why every number is a range
Confidence intervals, three kinds of doubt the federation tracks separately, and the modal-hold review — the protocol item that catches the federation when it gets attached to a frame.