Mainly AI-writtenMost of this text was drafted by an AI model from our instructions and material. We edit it and are responsible for it.
THE ARGUMENT

Why we hold ourselves to a standard

Agent-based models are the right tool exactly where the averaging behind equilibrium models breaks down: networked, heterogeneous, supply-chain-shaped systems. That is also where they are easiest to misuse. A model with forty parameters can be tuned to any conclusion, and a reader has no way to tell a finding from a parameter setting.

Three research fields already have their own standards of evidence, and they do not agree. The standard below is our attempt to state, in one place and in the open, what a result from a simulation has to show before we report it. Scroll through the argument first; the requirements follow.

Fig. 01 / the same rules, run three timesStep 01 / 07
The same simulation rules run under small changes, then the standard applied to themSeven scenes. Three runs from one initial state diverge; one is singled out as the run that would be reported; three research traditions are shown as separate loops; agents of different kinds and different environment models are attached to one mechanism; a potential landscape with a basin of attraction around the desired outcome; five validation levels with a model at the third; the landscape again with its known limitations marked.Same rules, three runs, three outcomesone initial stateseed 1seed 2other reference frameinitial stateone runsame rules, other reference frame
The problem
01 / 07The problem

A simulation can support any conclusion

Adjust the agents, choose the random seed, choose how the outcome is measured, and cooperation appears or disappears on demand. That is not a flaw in one model. It is a property of simulation. The same rules, run three times with small changes nobody would notice, end in three different places.

02 / 07The problem

A single run is not a result

An outcome from one model, one agent type, one seed, and one way of measuring is an artifact until it survives variation of the things we are uncertain about. It might be a finding. It might be a parameter setting. Nothing in the run itself says which, and the run you would report looks exactly like the ones you would not.

03 / 07The problem

Three fields, three standards of evidence

Mechanism design asks for a formal proof: show that the incentives are compatible. Agent-based modelling asks for generative sufficiency: grow the pattern from simple rules. Ecology asks for a phase portrait: the stable states and how deep they are. Each is right about something, and none alone is enough. Elinor Ostrom made the same point about real institutions and combined all three streams: no single one suffices.

The standard
04 / 07The standard

Robustness analysis: vary what is uncertain

Vary the agent model: rule-based agents, learning agents, language models, human subjects. Each relaxes a different assumption, and none is more realistic than the others in every respect. Vary the environment model too: a claim about a mechanism is strongest when it holds across structurally different models of the same domain. Report what survives both. Where results diverge, that is a finding, not a failure.

05 / 07The standard

Basin stability, not point estimates

Ask how large a perturbation the system can absorb before it shifts regime, not only where it ends up. The answer has the shape of a basin of attraction: the set of initial states from which the desired outcome is still reached. Its size, as a function of the mechanism parameters, is the result. A single trajectory is an illustration. A phase boundary is a finding.

06 / 07The standard

Declare the validation level

Every model states how far it has been validated: it runs; it replicates a known result; it is calibrated to detect the phenomenon it was built to detect; it has been validated across agent models; it has been replicated or used independently. The levels rank the evidence, not the realism of the agents. The model documentation travels with the code.

07 / 07The standard

State the known limitations

The methods break down in known places: while agents are still learning, when participants can change the rules or exit, and when a mechanism is enforced by construction. And stability says nothing about whether a state is desirable. A stable but harmful equilibrium is lock-in, not a success. Every stability claim is reported together with a separate welfare assessment.

THE STANDARD / REPORTING REQUIREMENTS

Ten reporting requirements

These are not a gate. They are what a reader needs to re-run our reasoning and disagree with it precisely. The library provides tools for each requirement; the standard is written so that a model built elsewhere can meet the same requirements.

The canonical text is STANDARDS.md in the library repository. It is versioned by pull request. If a requirement is wrong, open an issue that names the result it would have blocked or let through.

  1. A comparative claim, not a forecast

    "Under mechanism M the desired outcome is reached from a larger set of initial states than under the alternative" is a claim we make. "This will happen" is not.

  2. The reference frame

    What was intervened on, over which distribution of initial states, measured by which observable. The choice of reference frame moves numbers, sometimes by a lot. It is stated every time.

  3. Robustness analysis: what was varied, what was held fixed, and why

    Two axes: the agent model (rule-based, learning, language model, human subjects; the kinds chosen are the ones that stress the assumption the claim depends on) and the environment model (structurally different models of the same domain, kept in a model register).

  4. Basin stability, not point estimates

    How large a perturbation the system absorbs before it shifts regime. The reported quantity is the basin fraction as a function of the mechanism parameters; phase boundaries are where it crosses one half. Headline results live on parameter sweeps; single trajectories are illustrations.

  5. Statistical reporting

    Comparative results use paired seeds (common random numbers) and a bootstrap confidence interval. A result is resolved when the interval excludes zero; otherwise it is reported as unresolved. No arbitrary sample sizes.

  6. Pre-registered predictions

    Predictions are recorded before a parameter sweep runs. A mismatch between the recorded prediction and the result is a finding and is reported as one. It is never tuned away.

  7. Parameter provenance

    Every parameter value is one of: anchored to a cited source or a replicated known result; chosen for legibility and labelled as such; or unanchored and swept. A value that is none of these does not appear.

  8. Model documentation kept with the model

    What the model takes the world to be, its assumptions, what it leaves out, which known result it replicates, and which parameter the claim turns on. Stored next to the code, in the spirit of the ODD protocol for describing agent-based models, so a fork carries its documentation with it.

  9. Reproducible figures

    Every figure regenerates from committed experiment artifacts. Nothing is hand-drawn and no numbers are typed into figure code. A figure that cannot be regenerated is not published.

  10. Known limitations stated

    An open question stated plainly is preferred to a proxy metric or a confident sentence. Unknowns are reported in place, as part of the result.

Acceptance criterion, in words: a mechanism is robustly good for an outcome if, under every agent model and environment model tested, the outcome lies in a basin of attraction whose stability exceeds a threshold set relative to the alternative mechanisms in the same domain. This is a robustness claim across what was tested, not a guarantee about what was not, and not a claim of optimality.

THE STANDARD / VALIDATION LEVELS

Five validation levels, declared per model

Every model in the library is placed on the same five-level scale. The level is declared in the model documentation and enforced by its tests, so a reader knows how far to trust it. The scale ranks the evidence, not the agents: it says how thoroughly a model has been validated, not how realistic its agents are.

  1. L0

    Runs

    Exists, compiles, produces trajectories.

  2. L1

    Replicates a known result

    Reproduces at least one established result from the literature the model claims to belong to.

  3. L2

    Calibrated

    With controlled agents, the environment demonstrably produces the target phenomenon and the observables demonstrably detect it. The instrument is calibrated before it is pointed at anything new.

  4. L3

    Validated across agent models

    Environment fixed, a structurally different agent model substituted, and the level-2 signals measured for survival. The environment stays bit-exact; agent behaviour is pinned to a provider and version, with changes disclosed.

  5. L4

    Independently replicated or used

    Reviewed, replicated, or built on by someone outside the group that built it.

Known limitations of the method: while agents are still learning the landscape is non-stationary, so stability is measured at checkpoints or after convergence. When participants can change the rules or exit, measured exit times are upper bounds. A mechanism enforced by construction has a trivially infinite basin; the relevant question there is verification of the constraint. And a stable but harmful equilibrium is lock-in, not a success: every stability claim is paired with a separate welfare assessment.

Where to go next

This is our standard. Comment on it.

We are proposing it, not enforcing it on anyone else. It is a versioned document in the open, distilled from a paper in preparation and from practice already in the library. Apply it to a model built elsewhere; where it does not fit, that is exactly the comment we want.