← the scenarios

Economic scenarios — methodology

A what-if engine for AI's labor & growth impact. The invariants say what must hold; this page says why.

0. What this is

A what-if engine, not a forecast. The economic scenarios module lets you move five drivers of AI's labor-market impact and watch GDP, jobs, wages and the labor–capital split respond, beside live US baseline data. It is an independent, open implementation inspired by and calibrated against the published reference scenarios in Anthropic's *Economic Scenarios for Transformative AI* (Korinek, Jones, Sacher, Cotter, McCrory, 2026). It is not endorsed by Anthropic and reproduces none of their text, charts or assets.

Every number on screen carries a provenance flag — LIVE, FILED, GUIDANCE, ESTIMATE, STALE or USER — and live values set the sliders' defaults; they are never locks.

1. The chain, stage by stage

Jobs are bundles of tasks (the O*NET taxonomy). For each knowledge-work task, AI can leave it unchanged, augment it (assist a human), automate it (do it without a human), or a new task is created. The five drivers:

DriverMeaningRange
Capabilitiesshare of knowledge tasks AI can do0–100%
Adoptionof those, the share where AI is actually used0–100%
Autonomyof AI-used tasks, the share done without a human0–100%
Productivityoutput multiplier on AI-affected tasks1×–10×+
Adjustment speedmonths for a displaced worker to find new work1–36+

From these the model derives task penetration, a concave GDP response, a labor→capital share shift, wage changes by worker group, and worker-flow and unemployment outcomes. The full equations and calibrated coefficients are documented in the repository's docs/ECON_MODEL_SPEC.md.

Worked scenarios

2. Why the invariants are economics

Each invariant encodes one claim that must always hold:

3. How the two models connect

The capex model answers *who gets paid to build AI*; this one answers *what the build does to jobs, wages and growth.* They are linked by one explicit bridge: the capex model's solved system-capex ratio feeds a transparent, monotone elasticity that sets this module's capability, adoption, autonomy and productivity defaults. The bridge moves only defaults — you can always override them — and it is flagged ESTIMATE: *this link is a judgement call, not an empirical estimate.* There is no feedback the other way; the labor model never changes the capex solve.

Read distributionally, the labor-share loss and the fall in knowledge-worker wages are the household-side reading of the same "mortgage on the future" that the capex model's depreciation wall measures on the balance sheet. See the capex methodology §6.

4. Sources and known limitations

Live and derived data

What the model does not do

Following the report's stated limitations and adding our own: no policy responses, no business cycles, no aggregate-demand effects, no data-centre build-out demand, no robotics or physical automation, no individual-worker trajectories, no catastrophic risks, and no feedback from the labor side back into the capex model. The factor-share and wage coefficients are calibrated to three published points, not estimated from micro-data — they are ESTIMATE and editable in the assumptions panel, where an override flips the field to USER.

Required disclosures