DEFINE-UK ecological stock-flow

DEFINE-UK

The working paper behind the adapter, with its citation.

define-uk · UK · experimental · 31 pages

DEFINE-UK: running and gating an unlicensed ecological stock-flow consistent model

What the paper establishes: one gate passes, one diverges, two close at a ceiling.

The gates in one paragraphTable 4 · emissions · the scenario ceiling · deltas only

The manual’s Table 4 macro block replicates, with 2025 growth clearing a tolerance set after the run; baseline emissions diverge and are pinned rather than tolerated; and with no numeric v1.1 scenario results published, the scenario targets are closed at the achievable ceiling, not passed. The upstream is unlicensed and the baseline sits far from outturns, so the adapter serves deltas, never levels. The numbers are on Validation →

Your browser can’t display PDFs inline. The paper is 31 pages — open or download it instead.

Open the PDF
31 pages · pdf

Inline PDF viewing is unreliable on mobile browsers, so it’s disabled here. Open the paper in your device’s PDF reader instead.

Open the PDF

Source & reproduction: papers/define-uk/ on GitHub  ·  Replication report →  ·  All papers →

Cite this work

Ahmadi, Vahid (2026). “DEFINE-UK: running and gating an unlicensed ecological stock-flow consistent model.” PolicyEngine Macro working paper. https://policyengine-macro.vercel.app/papers/define-uk

@techreport{policyengine2026defineuk,
  title       = {DEFINE-UK: running and gating an unlicensed ecological stock-flow consistent model},
  author      = {Ahmadi, Vahid},
  year        = {2026},
  institution = {PolicyEngine},
  url         = {https://policyengine-macro.vercel.app/papers/define-uk},
  note        = {PolicyEngine Macro working paper}
}

No DOI is assigned.

Version stamp and authorshipWhich commit to cite · whose design, whose implementation

For an exact version stamp, cite the git commit of the artifact you used from github.com/PolicyEngine/macro. The model design belongs to its authors (George and Dafermos, SOAS); the replication and the clean-room implementation are ours, and are not endorsed by them.