.NOMOS — The protocol for computable authority.
The next era of civilization requires computable authority.
For centuries, authority lived in documents, procedures, and human interpretation.
Execution is becoming computational.
Authority must become computable too.
01 — THE PROBLEM
Civilization runs on authority.
Behind every action is the same question:
Who had the authority to make this decision?
For centuries, authority existed in documents, procedures, organizational structures, and human judgment.
That worked because humans were the execution layer.
But authority was never portable, machine-readable, or independently verifiable.
Now machines execute decisions.
Authority must evolve.
02 — THE SHIFT
From intelligence to authority.
AI produces
But it cannot know
Intelligence answers
What could be done?
Authority answers
What is allowed to be done?
.nomos provides the missing layer.
03 — THE HIDDEN LAYER
Intelligence cannot scale without formalized logic.
Every organization runs on an invisible decision system.
Rules. Exceptions. Judgment. Risk boundaries.
This operational logic determines what actually happens.
But today, most of it exists informally — inside documents, conversations, and human memory.
When intelligence accelerates execution, informal logic becomes systemic risk.
If logic is informal, entropy is invisible.
Today
With .nomos
Operational Logic Infrastructure is the discipline. .nomos is the artifact it produces.
Read the full paper →04 — THE PRIMITIVE
The .nomos artifact.
.nomos turns authority into an artifact.
What's inside
A portable representation of institutional intent.
View the full artifact spec →THE AUTHORITY STACK
.nomos is not trying to solve everything. It owns one layer.
Authority
Permission to act
Reasoning
Validity of conclusions
Evidence
Truth of inputs
Different layers. Different primitives.
05 — WHY NOW
Every major transition required new trust infrastructure.
Humanity digitized:
But authority remained trapped in documents.
.nomos makes authority computable.
06 — BEFORE, NOT AFTER
Authority is not something you discover in an audit. It is something you query.
Today, institutions answer one question: "Was this action allowed?" — after it happened.
An auditor reviews the transaction. A regulator investigates the decision. A compliance team discovers the breach.
The world governs in retrospect.
A .nomos artifact inverts the question: "Can this action execute under valid authority?" — asked before anything happens, answered deterministically, every time.
Governance as documentation
Governance as infrastructure
Aviation does not learn about safety from crashes. Constraints are checked before flight.
Query the authority — before the action
The future of governance is not proving an action was allowed after the fact. It is making unauthorized actions impossible before they occur.
07 — THE ECOSYSTEM
One protocol. Multiple layers.
Create Authority →
The creation layer
Transform institutional intent into a .nomos artifact. Studio is like a compiler for authority.
Input
Output
Signed .nomos artifact
"Private schools in Dubai may increase tuition fees only with KHDA approval, within the cap set by the school's inspection rating."
↓ becomes
{
authority: "KHDA School Fee Framework",
rule: "feeIncrease.approval",
constraint: "increase <= ratingCap",
condition: "khdaApprovalRequired"
}Studio = create authority
Govern Authority →
The system of record for the authority graph
Versioning, lineage, inheritance resolution, approval workflows, distribution, audit history, lifecycle management.
Git manages code lineage. npm resolves dependencies. Registry does both — for authority.
Registry = govern authority
Execute Authority →
The missing layer — the agent era creates this requirement
Guard sits between an autonomous system and action: is this action permitted by a valid authority artifact?
Guard is an MCP (Model Context Protocol) integration. Wrap a server you already run — GitHub, Postgres, Stripe — with zero code changes:
npx nomos-guardGuard = enforce authority
How Guard works — two integration paths →Discover and Exchange Authority →
The network layer, not just a marketplace
Already publishing
Exchange = distribute authority
GOVERNMENTS
The foundation for accountable autonomous administration.
A ministry policy becomes a verifiable artifact. A regulatory decision becomes independently auditable.
ENTERPRISES
From AI assistants to governed AI operators.
DEVELOPERS
The authority layer for agents.
TRY IT
Verify an artifact.
Drop a .nomos file. Instantly verify it. In the browser. No signup. No API key. No sales call.
Verification output will appear here.
Checking .nomos artifact...
KHDA — the Knowledge and Human Development Authority — regulates private schools in Dubai. This artifact seals its school-fee rules: a tuition increase is only authorized with KHDA approval, within the permitted cap.
The internet made information transferable.
AI made intelligence scalable.
.nomos makes authority executable.
Authority that can be executed by machines and verified by anyone.
Written law · Accounting · Standards · Networks · .nomos
That is what .nomos provides.