A NOMOS Protocol servicenomosprotocol.com
The rule of recognition, computable

Which laws govern this act?

Before any rule can be checked, something must answer a prior question: which rules apply at all. Today that answer comes from the actor — and the party that chooses which rules to check is the party that benefits. NOMOS Resolution answers it independently: the complete set of governing authorities, drawn from registrar records the actor cannot influence, with evidence that nothing was left out.

An open standard — NOMOS-SPEC-014, Active since 13 November 2026, independently implemented — with published conformance vectors and a machine-checked core. No account, no API key, nothing to trust.

Resolution statement · specimen
RESOLVED
for: jurisdiction = EU · established_in = EU · at 2026-11-13T09:00Z
The applicable set
Regulation (EU) 2024/1689 — the EU AI Act v1.0
claimed by its registrar, within a certified scope
Completenessclosure statement, fresh
Evidencelog head e3b0c442…
re-derivable offline from the public log
Notice · 13 November 2026NOMOS-SPEC-014 became the first NOMOS specification to leave Draft: an independent resolver, built from the published text alone, passed every conformance vector and necessity ablation then published.Read the record →
The set comes from the law's own records,
never from the one who acts.
Complete, or it says so

An answer is RESOLVED only under a registrar's signed statement that the enumeration is whole. Silence is never permission.

Conflicts are surfaced

Where two authorities both claim precedence, the system names the conflict for a person. A machine never quietly ranks sovereigns.

Checkable by anyone

Every answer carries the log heads it was derived from. Any party, with no relationship to us, can recompute it offline.

Why this exists

Institutions have solved a problem like this before

In 1973, banks faced a trust problem: how do you act on an instruction from an institution you have no private arrangement with? SWIFT answered it for messages — a common format, a directory of who's who, an authenticated network — and became the rail the world's money runs on.

Software agents acting for institutions face the same problem one level up. Not "did this institution send the message" but "which institutions' rules govern this action at all — and is that the whole list?" No directory answers that today. The actor assembles its own list, and every check that follows inherits the omission.

Resolution is that directory — with one deliberate difference from every directory before it: there is no network in the middle, and nothing to disconnect anyone from. Registrars publish signed, append-only records; relying parties choose which registrars they trust; verification happens where the action lands, offline.

The mechanism

Three records, one answer

01
Registrars you pin

A relying party decides, in advance, whose word counts: the registrars it recognizes, by root — exactly as it already pins certificate roots. The actor has no vote.

02
Claims within certified scope

A registrar’s record that a law applies binds only inside the scope its certificate grants. A genuine key claiming a stranger’s sector is void where it exceeds the certificate.

03
Closure, or the answer stays open

The registrar signs a statement that the list for this scope is complete and current. Without a fresh closure, resolution answers INCOMPLETE — named, and never read as permission.

What it answers

Three honest answers. Never a guess.

RESOLVED

The applicable authorities, complete under a fresh closure statement. An empty set is a real answer — no listed law applies — and it is proven, never assumed.

CONFLICT

Two registrars assert exclusive precedence over the same act. The conflict is surfaced with both claims on the record — settled by people, never by the resolver.

INCOMPLETE

A fact is missing, a pinned registrar is unreachable, or a closure has gone stale. The gap is named, and for a consequential act it is never read as permission.

840
published cases: 33 vectors, 34 registrar-log, 773 derived mutants
9
necessity ablations — every rule shown load-bearing
2
implementations — the reference, and an independent resolver
Lean 4
machine-checked resolver core
0
accounts, keys or calls home to verify
Nothing here asks for your trust.

The registrar's records live on a hash-chained, signed public log. One command, no dependencies, recomputes every entry and checks the head signature.

node verify-exchange-log.mjs --url https://www.nomosprotocol.com --catalogue
Who runs this

Governed like the rails institutions already trust

The roots and registrar rules are to be held by a cooperative of participating authorities and institutions — the NOMOS Protocol Working Group — with NOMOS as the operator under contract, on the model that has governed interbank messaging for fifty years. Until that body is seated, NOMOS operates the first registrar with the handover commitment published in advance. By design there is no chokepoint to capture: verification is offline, and every relying party chooses its own roots.

Read the governance model

Also: the Exchange, where the authorities themselves are published and queried.