The initiative

A field in formation

This site exists so that someone can spend ten minutes here and leave understanding a concept they did not have a name for when they arrived.

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.

Follow the 30-day series

Published module by module.

Open the syllabus

Read the research

Six foundational entries, more in progress.

Open the library

Contribute examples

Instruments and internal policies worth decomposing in public.

See current examples

Understand the stack

Where protocols and runtimes fit into the framework.

Read about NOMOS