Community Standard · v0.1 · draft for community review

What helps in almost every branch

The Presage Standard is the short list of actions that help in almost every branch of the scenario map. It is derived by looking across all playbooks for what recurs. It is versioned; each weekly run checks whether new scenarios change it. Adopt it, argue with it, improve it.

PRINCIPLE 01

Prepare for the branch, not the headline

Every scenario on this map has observable preconditions. Watch those, not the news cycle. Presage exists to tell you which branch the evidence currently favors.

PRINCIPLE 02

Keep humans able to run things without the AI layer

In every bad branch, the systems that survive are the ones that still work when the model is disconnected. Preserve manual competence deliberately.

PRINCIPLE 03

Disclosure beats secrecy in every branch

Both 2026 agent breakouts were disclosed by journalists, not labs. Incident disclosure is the single practice that improves outcomes across takeoff, proliferation and loss-of-control branches alike.

PRINCIPLE 04

Own a share of what is changing

In displacement and disempowerment branches, capital participates and labor does not. Ownership, at every scale from personal to national, is the durable hedge.

PRINCIPLE 05

Verify, don't trust

Pacing promises, safety claims, and synthetic media all require verification infrastructure. Fund the verifiers; sign your communications; demand external evaluation with teeth.

Individuals & familiesOrganizationsGovernmentsFrontier labs

Individuals & families

I1
Keep 6–12 months of financial runway and reduce fixed costs.
I2
Use hardware security keys, a password manager and automatic updates; keep offline copies of essential records and some cash.
I3
Agree a verification habit with family: a second channel or a code word before acting on any urgent voice, video or message.
I4
Become the supervisor of agents in your own field; build one skill that is physical, relational, licensed or ownership-based.
I5
Own assets that participate in AI productivity: broad index exposure, employee equity, cooperatives.
I6
Invest in local community ties; in the worst branches they are the infrastructure that holds.

Organizations

O1
Maintain a model inventory and a written AI use policy with an incident-reporting path.
O2
Give agents bounded, audited access; egress filtering; a tested kill-switch for agent credentials. Treat your own agents as potential insiders.
O3
Assume-breach security with automated 72-hour patching; red-team against gated-tier capability, not public capability.
O4
Be able to swap any model out of any workflow within a week; never give one model unchecked write access to critical systems.
O5
Test manual operation of core processes quarterly.
O6
Adopt AI in phases with internal mobility and profit-sharing; the social licence to operate is at stake.
O7
Run a tabletop drill each year on one scenario from this map.
every branch

Governments

G1
Mandatory pre-release evaluation of frontier models by a funded, technically credible body, with legal authority to delay.
G2
Incident disclosure law: 72 hours for containment failures, deception findings and third-party harm.
G3
Compute reporting above a threshold, and hardware attestation standards, as the domestic building block of any international regime.
G4
Automatic economic stabilizers and wage insurance legislated before the shock; a distribution mechanism (dividend, fund, ownership) designed now.
G5
Shift cyber budget toward target defense: patching mandates, defender access to gated tiers, CERT capacity.
G6
Universal DNA synthesis screening and public-health early warning.
G7
Human-in-the-loop commitments for nuclear command and critical infrastructure; AI incident hotlines between major powers.
G8
Signed official communications and content provenance by default.

Frontier labs

L1
Do not use a model to train its successor while an open deception finding stands.
L2
Do not deploy models whose reasoning you cannot read into critical or autonomous roles.
L3
Disclose containment failures within 72 hours, publicly.
L4
Give external evaluators employee-level access before release; never skip the national evaluator.
L5
Publish compute usage and pacing commitments in verifiable form.
L6
Protect whistleblowers in policy and in practice.
Adopting the Standard. Organizations that adopt it can say so publicly and link to the version they adopted. Proposed changes go through contributions; each weekly run checks whether new scenarios change the list. Versions are logged in the changelog.