An emerging discipline
The emerging discipline of making institutional authority executable and independently verifiable
The emerging discipline of representing institutional authority in forms that machines can execute deterministically and independent parties can verify.
01The Field
Institutions express authority through policies, regulations, standards, contracts, and procedures. That authority is real, but it is carried by prose — and prose has to pass through a human before anything happens.
Computable Authority is the discipline of representing that authority in forms that machines can execute deterministically and independent parties can verify: bound to a version, evaluable against facts, reproducible years later.
Machine-Readable Policy is the first practical domain of Computable Authority, providing the methods for representing institutional policy in executable form.
Learning path
02The Problem
Today
Future
The step that decides the outcome is the one step that leaves no record.
Prose has no defined behaviour, no inputs, and no reproducible output.
At machine speed and volume, unrecorded interpretation becomes systemic risk.
03Machine-Readable Policy
The operative statements: what must, may, and must not happen.
The vocabulary the rules depend on, scoped and versioned.
The circumstances that activate, modify, or suspend a rule.
The evaluable structure that turns facts into an outcome.
The discipline is not about digitising documents. It is about separating the authority an institution holds from the prose that has historically described it.
04The 30-Day Syllabus
Module 1
Days 1–7
Module 2
Days 8–14
Module 3
Days 15–21
Module 4
Days 22–30
05The Research Library
R-01 · 6 min
Authority is the right to decide. Computable authority is that same right, expressed so a machine can exercise it inside defined limits — and prove it did.
R-02 · 7 min
Capable models with no authority layer are not governed systems. They are fast improvisation with an institution's name attached.
R-03 · 5 min
A decision is only defensible against the rule that was in force when it was made. Almost no institution can produce that rule on demand.
R-04 · 6 min
Most policy disputes are not about rules. They are about what a word meant, to whom, and when.
R-05 · 8 min
The compilation pipeline: how a published instrument becomes an artifact a runtime can evaluate — without losing its provenance.
R-06 · 7 min
Institutions will exchange authority the way systems now exchange data — and that requires shared infrastructure, not shared documents.
06Examples
07The Stack
The stack
NOMOS Protocol provides infrastructure for creating, exchanging, and verifying machine-readable authority.
It is one implementation of the framework described on this site — not the framework itself. The discipline should outlive any single protocol.
How NOMOS implements the stack →08Join the Initiative
One module at a time, published as it is written.
New research entries and compiled artifacts as they are released.
Bring an instrument or internal policy worth decomposing in public.
Open questions, disagreements, and terminology that still needs fixing.