A field in formation

Institutions are about to delegate an enormous amount of decision-making to machines. The rules those machines will operate under are currently held in documents that no machine can read, interpreted by people whose reasoning is never recorded, and revised in ways that cannot be traced.

That gap has a name now: the authority layer. Building it is a discipline in its own right — part legal drafting, part systems engineering, part verification. This initiative documents that discipline as it emerges: the vocabulary, the failure modes, the open problems, and the worked examples.

What this is not

This is not a product site. NOMOS Protocol is one implementation of the framework described here, and it appears where implementations belong — at the end, after the ideas. If the framework is right, other implementations should follow, and the discipline should outlive all of them.

Editorial principles

• Define terms before using them. Ambiguity is the failure mode being studied.
• Show artifacts, not assertions. Every claim should be demonstrable on a real instrument.
• Name the open problems. A field that only publishes solved things is marketing.
• Keep applications downstream of the category. Any single deployment is an example, never the thesis.

Authorship and citation

This initiative is maintained as a public field guide for Computable Authority. When referencing it, cite the project name, page title, retrieval date, and URL so definitions and examples can be traced as the discipline evolves.

Suggested citation formats — plain text and BibTeX, for the discipline as a whole and for individual pages — are on the citation page. A machine-readable citation is also published as CITATION.cff.

The written content on this site — the Manifesto, the Laws, the syllabus, the research library, the glossary, and the illustrative examples — is licensed CC BY 4.0: reuse and adapt freely, with attribution.