I. Why Code After

Code After names a break. ^[1]

For most of modern history, code meant deterministic instructions executed by tools that did what they were told. Law, accounting, regulation, the architectures of authority that hold a society together — this is the inherited apparatus of modern governance. All of it was built on the assumptions that condition made available. Humans act. Tools execute. Responsibility is traceable. The instrument disappears into the result, and the result can be audited back to the person who caused it.

Stable couplings hold throughout — between action and attribution, between rule and execution, between representation and reality. Call this the Pre-Code condition. The distinction is structural rather than chronological — Pre-Code names not a period before software but a regime in which code, however sophisticated, behaved as deterministic instrumentation subordinate to human intention. Most of the institutions a citizen, a regulator, a court, an auditor, or a policymaker uses to make sense of the world today were designed for it.

The condition no longer holds. AI systems operate as probabilistic, adaptive, and partially opaque agents. They generate knowledge, shape decisions, and participate in economic and institutional processes in ways the inherited languages of evidence, liability, compliance, and sovereignty were not designed to describe. The break is not technical. It is conceptual. A Pre-Code ontology is being used to govern Post-Code actors, and the mismatch produces structural failure at every point where the two are required to meet. The term actor here is functional rather than metaphysical: a system whose outputs participate materially in institutional processes, regardless of whether the system itself possesses agency in the human sense.

Code After: Law, Accounting, and the Governance of Artificial Intelligence (v0.9, April 2026) named the break and developed it inside one area of institutional life — governance — through four structural gaps. The Code After Series extends the operation. If probabilistic intelligence is becoming a quasi-agent — capable of shaping outcomes without being a legal subject in the inherited sense — inside education, work, evidence, measurement, jurisdiction, and language itself, then each one requires the same procedure: a diagnosis of what the inherited instruments no longer reach, and a rewritten operating logic for what now has to be governed.

The project supplies the vocabulary and analytical structure for that transition. Not from one technology to another. From a civilisation in which human intelligence was the only intelligence participating in institutional decisions to one in which it is not — and from one organised around deterministic tools to one co-built with probabilistic intelligences. This is the why of the project. What follows is the what — the people the work is built for, the time available to do it, and the publication architecture through which it will be done.

AI is being built by a very small number of people, working in a very small number of labs, concentrated in a very small number of places, for a world that includes almost everyone else. This is not a complaint. It is a description of the present moment. The capital, talent, compute, data, and institutional concentration required to build frontier AI systems exist at scale in the United States and China, and at partial scale in the United Kingdom and a short list of adjacent economies. The consequences of what is being built will be carried by the roughly eight billion people who live everywhere else.

The gap between who is building AI and who will live with what it builds is the defining inequality of the period. It is wider than any comparable gap in the industrial transition, which unfolded over a century while the AI transition is unfolding over a decade. It is also less visible. Earlier technologies let a user build a working picture of the machine through interaction. One could watch the machine, follow the process, work out the rule. AI systems break that learning. The output arrives without the reasoning that produced it, and often without reasoning in the human sense at all.

A person can use AI fluently without any reliable account of how it works. This is the structural reason the gap widens faster than understanding can catch up. It is also the everyday face of the Pre-Code / Post-Code break — the reason an ordinary user, in an ordinary interaction, can no longer learn the system through use.

The Code After project exists to narrow this gap through translation. Not technical translation — the work of explaining how large language models work, which others do well — but institutional translation. What is changing in the laws, the economies, the credentials, the languages, the systems of evidence, and the structures of authority under which ordinary lives are lived. What the changes mean for the people affected by them. What action is still possible, in the time before the new institutions settle into place and the old ones lose the capacity to reach them.

I write for the majority of the world that does not currently have a voice in the discussion and cannot afford not to have one. Citizens, professionals, policymakers, and the institutions that serve them, in every part of the world outside the frontier economies and in most parts of the frontier economies themselves. Writing for this audience requires a specific publication objective and process, which Section VI describes, and a specific discipline in how the writing is done, which Section IX sets out in full. Together, the publication process and the writing discipline establish the series as the continuation of the work v0.9 began.

1. Code is retained as the term throughout this project because the institutional infrastructures of the AI era remain computationally mediated even after deterministic execution ceases to be their defining characteristic. The project name marks a change in what code is, not a renunciation of the term. ↩︎