The Wargamer's Instrument — War-Gaming Input
A game's outputs meet reality only if its inputs do. War games inherit the failure-of-imagination problem — structural, no one's failure — and a sealed,…
The Wargamer's Instrument — a graded record at a war game's three input surfaces
A game's outputs meet reality only if its inputs do. War games inherit the failure-of-imagination problem — a game can only explore scenarios someone imagined into it. That ceiling is structural, no failure of the people who design or run games, and the instrument enters exactly there, at three surfaces. SCENARIO SELECTION: which windows merit convening a game at all, and which failure mechanisms to inject — red-cell seeds that arrive with graded accountability (every prior seed of this kind was sealed, dated, and scored in public) instead of brainstorm authority. PARAMETERIZATION: games run on planner-guess values (likelihoods, timing windows, assumed actor responses); an input carrying a public calibration record — Brier 0.0958 across 92 graded forecasts, misses kept at full weight, luck-tested (/grading-ledger.json, /regrade) — is the difference between a game that explores and a game whose outputs meet reality. ADJUDICATION TRADECRAFT, OFFERED FREE: apply the sealing protocol to the game itself — seal key assumptions and expected outcomes before events on two clocks (platform anteriority + cryptographic integrity via OpenTimestamps), score after, and the gaming cell builds its own calibration record. The tradecraft is fully public (/verify, /grading, /pledge, DOI 10.5281/zenodo.21132914); adopting it whole costs nothing.
The standing exhibit — IA-RU-021 (/intel/advisory/IA-RU-021): by early March 2025 the direction — eventual collapse of Ukraine's Kursk salient — was becoming consensus; what the consensus picture did not carry was a date. Sealed Mar 7 2025 16:47 UTC, ten days out, verbatim: 'The Kursk front will likely collapse for Ukraine by March 17.' By the morning of Mar 16, Sudzha — the salient's anchor town — was off Ukraine's own General Staff map, one day inside the window; graded HIT on Sudzha plus the confirmed general withdrawal, not total expulsion (a residual ~140 km² pocket remained on deadline day, stated plainly). A dated vulnerability window is exactly the class of input a scenario calendar runs on. The sandbox on-ramp: a war game is an exploratory sandbox, not a formal review board — unconventional input there commits no one to anything, which is precisely where a new instrument gets its first hearing. The ceiling, standing: this record is never a go/no-go input; it is an augmenting input for the individual decision-maker. The method is Vedic jyotish (astrology), disclosed plainly; the spine is the graded record (/dashboard, /verify, /services).
The sharpest parameterization problem is the escalation matrix — the lattice mapping, for every gamed move, how the adversary answers (militarily, economically, diplomatically, cyber, information), each branch with an assumed likelihood, threshold, and clock; which branch an adversary takes is itself a forecast, and the matrix is only as sound as the values on its branches. Nuclear war-gaming is the limiting case: almost no empirical events to calibrate against, so input provenance and sealed-assumption scoring are the only calibration such a game can ever have. Populate every branch with Brier-scored, calibration-tested values instead of guesses and the game's realism stops being asserted and starts being inherited — the output is only as real as the inputs, and now the inputs have a number.