An emerging discipline
Making institutional authority executable by machines and verifiable by anyone who did not write it.
Institutions already write their authority down — policy, regulation, standard, contract, procedure.
The discipline asks:
What has to be true of that writing for a machine to run it, and for a stranger to check the run?
Why now
AI systems can execute decisions at a scale no institution was designed for. Documents were written for human interpretation; machines require authority that is explicit, executable, versioned, and verifiable. Computable Authority studies how institutions make that transition.
As software becomes capable of acting autonomously, authority can no longer remain a human-only interpretation layer. Machines must be able to determine not only what they can do, but what they are authorised to do.
01The Field
Institutional authority is real, but its operative representation is usually carried through prose — which means a human must interpret it before a machine can act.
Representing it computably means binding it to a version, making it evaluable against facts, and keeping it reproducible years later.
Machine-Readable Policy is one of the first practical domains of Computable Authority, providing methods for representing institutional rules in executable form.
What Computable Authority studies
Computable Authority studies how authority can be:
Learning path
02The Problem
Today
Future
The step that decides the outcome is the one step that leaves no record.
Prose describes authority for human interpretation. It does not define a deterministic execution model with explicit inputs, outputs, and reproducible results.
At machine speed and volume, unrecorded interpretation becomes systemic risk.
Authority became readable with writing. It now needs to become computable.
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–6
Module 2
Days 7–12
Module 3
Days 13–18
Module 4
Days 19–24
Module 5
Days 25–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 · 10 min
Institutions will exchange authority the way systems now exchange data — and that requires shared infrastructure, not shared documents. Three prior efforts got partway there; none closed the gap.
R-07 · 18 min · Position Paper
The emergence of autonomous AI agents changes the problem that Law as Code needs to solve — and requires more than machine-readable law. It requires machine-computable authority.
R-08 · 13 min · Position Paper
Existing guardrail architectures treat authority as a filter applied after an autonomous system has already decided what to do. This paper proposes bounded contextual authority — a portable, machine-verifiable representation of the mandate an autonomous system acts under — and decomposes precisely which part of the resulting handshake problem is already solved and which is not.
R-09 · 18 min · Design Note
NOMOS's trust primitives — sealing, third-party attestation, revocation, and chain-of-trust key certificates (now published as NOMOS-SPEC-007, Draft) — all assume a relying system already has reason to trust the root key an authority chain is checked against. This note proposes a candidate governance model for that root, then deliberately red-teams it against web PKI, DNSSEC, RPKI, Certificate Transparency, accreditation, professional licensing, treaty recognition, and federated trust — and reports plainly what survives and what does not.
R-10 · 12 min
Organizations are not rule-executing systems. They are emergent decision systems whose true structure is not documented, but inferred from behavior under constraint.
R-11 · 14 min · Engineering Case Study
Why chunked LLM extraction fails on legal documents longer than roughly thirty pages, and the architecture that fixes it: separate indexing from extraction.
06Examples
07Reference Architecture
Computable Authority defines the discipline. NOMOS is a working protocol implementation.
How NOMOS implements Computable Authority →08Join the Initiative
Primary
Receive new research, syllabus lessons, and machine-readable authority examples as they are published.
For people working in policy, AI governance, government, and academia. No product marketing.
Secondary
An instrument or internal policy worth decomposing in public.
Work from legal theory, formal methods, or AI governance that belongs in the library.
The vocabulary of the field is still being fixed. Argue with the glossary.
Work through a compilation and verification pass alongside the initiative.