Interventions

Pull one lever, see what moves.

An intervention is a parameter of a run. Set it, run the world, and compare the run with the one before it, line by line.

A geoeconomics simulation on a globe in the CommandAGI workbench: oil flows from the Persian Gulf to China, India, Japan, South Korea, Europe and the United States drawn as arcs, each country coloured by its oil inflow, while the globe turns slowly from the Gulf toward the Pacific.
Recorded in the workbench: the geo-hormuz world on its globe. Its numbers are illustrative, not data.

A lever

The lever is in the file.

A world declares its parameters with their bounds. A run records the values it ran with, so an intervention is never a hidden edit.

How an intervention becomes a runThe world declares three parameters with bounds: Iran's escalation, Saudi Arabia's exposure to the strait and the complementarity of pressure. A person or an agent sets them for a run. The run's run.json records them in simulator.settings before the engine steps, so the run can be compared with any other and run again.parametersescalation 0–3 ·sa_exposure 0–1 ·complementarity 0–0.6A person or an agentsets a valuerun.jsonsimulator.settings:param.escalationThe enginesteps the same sceneCompare runsthe same fields, side bysideHow an intervention becomes a runThe world declares three parameters with bounds: Iran's escalation, Saudi Arabia's exposure to the strait and the complementarity of pressure. A person or an agent sets them for a run. The run's run.json records them in simulator.settings before the engine steps, so the run can be compared with any other and run again.parametersescalation 0–3 ·sa_exposure 0–1 ·complementarity0–0.6A person or anagentsets a valuerun.jsonsimulator.settings: param.escalationThe enginesteps the same sceneCompare runsthe same fields, side by side

The run names its lever.

The run that ships with the world records the values it ran with. Any run you make records yours the same way.

cloud://global/examples/template-library/worlds/geo-hormuz/runs/20260928t132000z-if0l/run.jsonthe shipped run's file · simulation
{
  "of": "../../world.tsx",
  "reality": "simulation",
  "title": "geo-hormuz: 120 days, escalation 1.8 (synthetic)",
  "simulator": {
    "driver": "sim",
    "settings": { "hz": 1, "record_hz": 1, "param.escalation": 1.8, "param.sa_exposure": 0.6, "param.complementarity": 0.3 }
  }
}

Three interventions

Escalation 1.2, 1.8, 2.4: the price follows.

The one engine stepped the world three times with only escalation changed (case-studies/hormuz/stats.json).

Recorded before it runs. A command a principal gives a running simulation is recorded before the engine gets it, then the step it took effect at. Fork, then change. Fork a run at a moment and set a lever from there. The fork names the run it came from. Honest about the model. This world's numbers are round numbers of the right order. It says so in its own description.

peak at escalation 1.2
$90.5
peak at 1.8
$117.3
peak at 2.4
$144.1

Simulated

Oil price under three levels of escalation, USD a barrel
The numbers
Oil price under three levels of escalation, USD a barrel
DayEscalation 1.2Escalation 1.8Escalation 2.4
0808080
10808080
20808798
3087108130
4089.5115140
5090.2117143
6090.4117144
7090.5117144
8086.6112136
9081.391.5109
10080.382.386.3
11080.180.481.2
1208080.180.2
ProvenanceFile cloud://global/examples/template-library/worlds/geo-hormuz/world.tsxOutput case-studies/hormuz/stats.jsonTool scripts/sites/case-studies.mjs hormuz: sim-engine.jsRan on This computer (dell-gb10-1)When

Try your own intervention.

Open the world and set its parameters.