Doctrine

v0.1 DRAFT · 2026-07-30 · What this manual is, how it is layered, and the rules every entry obeys.

What this is

Purposive Accelerationism argues that ungoverned techno-capital tends to totalisation, and that the response is to rebuild the governor natively, at machine speed, in the substrate itself. The book deliberately stops at naming the invariant each domain needs and pointing to the primitives that could secure it. This manual is the other half of that division of labour: the engineering companion, openly published and revised as the parts improve, so that nothing in the book dates with any particular configuration. The book is the argument; the manual is the workshop.

It is written for the coalition the book names: cryptographers and protocol engineers, economists and mechanism designers, lawyers and theorists, artists and writers, and founders. Constitutionalists, in a word — anyone who takes up the writing of rules as the alternative to being ruled. No single guild can read all of every entry, and no entry requires it: take the layer you build at, and the composition notes will tell you who you depend on.

The layered form

A field manual worth the name is layered, and this one has three strata that age at different speeds. Doctrine — this page and the constitution — states why the manual works the way it does; it changes slowly and by amendment. Patterns are the working unit: recognised problems in the constitution of a domain, with the known ways of resolving them and the costs of each; they decay slowly, by proposal. Reference implementations are the perishable stratum — named parts, arrangements, parameters — dated on arrival and expected to be replaced. When an implementation goes stale, the pattern survives it; when a pattern is bettered, the doctrine survives that. Nothing here is canonical except the invariants inherited from the book.

The entry template

Every pattern states seven things, in order: the invariant it serves, cited to the book and never re-argued; the constitutive choices the founders must make themselves, deliberately left unfilled; the forces and capture risks, as the Trinity diagnostic names them — the pattern's tilt, and which vertex takes the domain if it ships alone; the pattern space, plural wherever plurality exists, with an entry flagged as a monoculture risk where it is not; the reference implementations, dated and replaceable; the failure modes; and the composition — which other patterns discipline this one, and what the stack needs from its layer to stay balanced.

The rules every entry obeys

Two rules govern the writing, both inherited from the book's own philosophical spine. The first is the no-destination rule: the manual specifies means of holding ends open, never the ends themselves. A manual that told you what your polity is for would be the general will in a server rack — the exact trap the book warns positive liberty falls into — so every entry hands the ends to the founders and prices the ways of holding them. The second is the de-personification rule: a mechanism regulates; it does not want, ask, choose or know. Purpose lives in reference values and constitutions, chosen by people, and the manual's grammar keeps it there.

A third discipline follows from the first two. The Trinity diagnostic that runs through every entry produces named risks, never scores. There is no purity rating here, no green tick certifying a protocol clean — those flatter the builder and invite capture of the certifier. An entry tells you where a pattern tilts and what that tilt costs; weighing it is your work.

How to read it

Builders should start at the parts inventory and climb; founders of collectives and polities should start at the layer they mean to constitute and follow the composition notes downward; readers arriving from the book should start with the constitution of the manual itself, which is the smallest worked example of everything the book proposes. Wherever you start, the discussion thread on each entry is part of the entry: the manual is extended by the people who use it, and the record of argument travels with the text.