Emergences · A diagnosis and a blueprint · 2026
Four crises are converging — ecological, geopolitical, technological, cognitive. Emergences reads them as one structural crisis, and answers with the Protocol: a blueprint for infrastructure, economics, governance, purpose and security that resists capture — published unfinished, to be examined, criticized and built.
Converging pressures
The institutions expected to respond operate in years and conference cycles. Ecological thresholds, automated systems and information shocks move in months, minutes and seconds. The mismatch is becoming structural — and several of its consequences do not reverse.
Planetary boundaries reported beyond their safe operating space.
Carried by the project's Diagnosis from planetary-boundaries assessments. Figure pending final verification against the cited assessment before production use.
Binding treaty limits remaining on the two largest nuclear arsenals.
Refers to the recorded expiry of the last bilateral arms-control treaty between the major arsenals, per the Diagnosis. Pending verification against primary reporting.
Share of global employment analysts report as exposed to AI-driven disruption.
An exposure estimate, not a prediction of job losses; methodologies differ widely. Pending verification against the cited institutional analysis.
IQ points per year of decline reported across later birth cohorts in one national study.
A single-country cohort study; causes are debated and replications contested. The Diagnosis carries the context. Pending verification.
A construction, not a prophecy
Emergences is the project. The Diagnosis is its assessment. The Protocol is its blueprint: commitments, one draft specification, and open research programs — designed so that power over shared infrastructure stays answerable, and alternatives stay possible.
No system can be made impossible to capture. It can be built so capture costs more than it returns — and so that people can always leave with their data, identity and relationships intact.
Accounting that cannot see energy and matter finances the destruction of its own base. Physical accounting begins at protocol scale; currency design remains research, not doctrine.
Every privileged role, key and mandate decays on a published schedule, renewable only by fresh consent of the governed. No permanent seats. No perpetual keys.
Security defends against outside attack and against capture by legitimate insiders — founders included. However grave the emergency, its powers are bounded, public, temporary and reviewed.
A connected system
Each pillar owns a distinct question, and each states openly how much of its answer exists — a specification where there is one, research where there is not.
Who controls the foundations nobody sees?
Draft specificationHow can value flow without devouring its own base?
Research programWho decides, by what right, and fast enough to matter?
Rules + open researchWhat is all of this for?
Normative compassWhat keeps an open system alive among adversaries?
Threat modelMaturity labels are commitments, not decoration — each links to the pillar's own account of what exists and what remains research. See the Protocol overview →
“This is neither the enchantment of progress nor its refusal. It is something the nineteenth century never managed: arriving before the damage is done.”
Built in public
The Protocol is published unfinished — to be examined, criticized and built. Its current state is recorded openly, including what has never been tested.
Draft v0.1, request for comments. Nine testable requirements; six named open problems. Awaiting independent technical review.
Draft specification derived from RFC-0001. Never yet executed, by anyone — and the project says so rather than implying otherwise.
Published at stated maturity, from draft specification to research program. Open questions and validation needs are documented, not concealed.
The Diagnosis draws on assessments from, among others:
Three doors
One crisis seen from four angles — and the wager that this time, the response can come before the damage.
If you are skepticalOpen problems are first-class content here. Disagreement, stated precisely, is the contribution the project asks for.
If you buildReference a requirement, propose a testable alternative. The annual hostile-fork drill has never been run — being first would teach everyone.
