For implementers
Resolution is NOMOS-SPEC-014 — open, vendor-neutral, CC BY 4.0. We hold ourselves to a rule most standards bodies don't: a specification remains a Draft, whatever we believe about it, until a second implementation — built from the published text alone, by someone with no connection to us — passes every published vector.
On 13 November 2026, two days after the specification was published, that rule was met.
An independent resolver — nomos-spec014-resolver, Python, standard library only — arrived hours after the open call, built from the specification text and the published vectors. It was verified before it was celebrated:
- Conformance vectors. 23 of 23, by exact verdict match
- Necessity ablations. 8 of 8 — C5, C6, C7, C8, CF: each attack succeeds under exactly its own ablation
- Order independence. byte-identical under 10-seed shuffling of every list in the world
- Vector integrity. suite pinned by SHA-256 · 7dfd2fca…f240bb — byte-identical to the canonical file
- Execution. green on its own CI, Python 3.10–3.13, GitHub runners — not ours
- Authors’ verification. read line by line before merge: no answer-matching; an architecture that is not the reference’s
Stated precisely, because precision is the product: the resolution algorithm is an independent construction from the text. The condition-grammar evaluator beneath it derives from our published Python reference — a delegation the open call's terms permitted in advance, since that layer belongs to SPEC-008, which is why SPEC-008's own exit remains open. The implementer's statement of method and attribution are on the record in their repository. Every word of this is in the standard's changelog, not a press release.
The proof stack
The resolver's core is mechanized in Lean 4 — the completeness and order-independence arguments are theorems, not prose. Writing that proof found two gaps in our own first draft; both became vectors. The discipline bites its author first.
Five named attacks — the carrier choosing the law, jurisdiction squatting, the zombie authority, the starved resolver, the misdescribed act — each with an ablation showing it succeeds when its condition is removed. Every rule is load-bearing, demonstrably.
Two implementations produce identical verdicts on every hand-written vector — ours, and a stranger's, against a file pinned by hash. A derived corpus of 773 further cases now tests agreement in bulk, including the one rule no hand-written vector had exercised. Interoperability is measured, never claimed.
The serious one is still open
An independent verifier for the Act: one exact action, carried with its proof of authorization, verified where it takes effect. 46 published vectors and 1,804 mutants. This is the keystone specification — its second name is still unwritten.
Also open — SPEC-014’s 0.4.0 additions. The specification has since grown: deferral, delegation by recognition, key rotation, and registrar logs run by the institutions themselves. Those additions are Draft until an implementation independently passes their vectors — the discipline never stops applying, even to an Active specification.
This is open-standard work, not paid work — and what it carries is what money doesn't buy here. As of 13 November 2026, none of it is hypothetical:
- Your name and repository written into the standard itself, permanently — as SPEC-014's record now shows, this is literal.
- A founding seat on the NOMOS Protocol Working Group, with review rights on future revisions.
- Named acknowledgment in the published Computable Authority papers.
- Every divergence your implementation finds becomes credited errata — break the specification and we thank you in writing.
Forty years ago, people implemented the early internet RFCs for exactly this — those names are still in those documents. On 13 November 2026, the first such name entered ours.