P-02 · Part III · NOMOS-SPEC-014 0.4.0
Resolution
Updated Nov 13, 2026 · Resolve the Law, Not the Catalogue
A commit means every law that applies, as far as the relying party's pinned registrars state it, was checked and allowed it, whatever the agent chose to mention.
Found by the proof · Nov 12, 2026
Two gaps in the first draft, both closed in 0.2.0
- A closure's list was never read. A genuine withdrawal hid law while an older closure still named it. Now a closure must agree with the registrar's own log, so hiding law takes a signed closure that omits it.
- A stale copy of a log looked live. A cached copy whose closure was still in bound answered with superseded law. Now a relying party bounds how old a copy may be.
Caught by this proof · 5 gaps, all closed
- A closure's list was never read
- A stale copy of a log looked live
- A test that tested the wrong attack
- An attack the design already prevents
- A combination order that would approve an undecided act
What each one was, and how it was closed →
Proved · Lean 4, core library, standard axioms
| Claim | Theorem |
|---|---|
| The order authorities are checked in never changes the verdict | combAll_perm |
| A commit means every in-force, in-scope law on every reached registrar was checked and allowed it | sufficiency, full_commit |
| The authorities an Act names are not an input | decide_ignores_presented |
| More law is never less safe: more registrars, or an extra claim from any key | reached_mono, add_claim_keeps_law |
| Under closure agreement, law a current closure names cannot leave without a new signed closure | hiding_needs_new_closure |
| Dropping C5, C7 or C8 commits a sanctioned payment from genuine entries alone | C5_necessary, C7_necessary_snapshot, C8_necessary_* |
| Dropping C6 only adds law: it causes wrongful refusals, never a wrongful commit | noC6_never_commits_more |
| Composed with Part II: a commit means every governing authority passed Part II's verification, legitimate, current and permitting the act on the true facts | end_to_end (Composition.lean) |
| Deferral (0.4.0) never removes law: with or without it the answer is the same, except a conflict may resolve, with exactly the laws required without it; only a registrar's own log can waive its precedence | deferral_never_removes_law, deferral_is_own, undecided_edge_incomplete |
| Delegation (0.4.0) never widens: a recognized registrar's law lies where its recognizer's certificate and the recognition both hold, and an unknown fact on the recognition keeps the answer open | delegation_never_widens, delegation_unknown_incomplete |
Attacks
Each attack uses genuine, correctly signed entries only. The reference resolver refuses every one, and each succeeds when exactly its own condition is removed, and under no other.
| Attack | Stopped by |
|---|---|
| Applicability hiding | C5 |
| Jurisdiction squatting | C6 |
| The zombie authority | C7 |
| The starved resolver · the stale closure | C8 |
| Withdrawal under a closure | C8 · agreement |
| The stale view | C8 · view age |
| The misdescribed act (0.3.0) | CF · context fidelity |
| Squatting through delegation (0.4.0) | C6 · the recognizer's certificate |
| A registrar's self-asserted scope (0.4.0) | certified scope from pins and recognitions only |
Not yet proved
- The walk over recognition edges. Theorems hold for the registrars the walk reached; the walk itself is tested.
- Delegation through several edges at once, and a registrar both pinned and recognized: tested by the vectors, not proved.
- Log heads, signatures, key rotation, forks and the view-age bound: tested by 34 registrar-log cases checked by two implementations, not proved.
- When two registrars' precedence truly conflicts, beyond the definition used (exclusive claims).
- Independence: one implementation so far. SPEC-014 stays Draft until a second resolver passes every vector.
Run it yourself
git clone https://github.com/nomos-spec/spec cd spec/papers/resolution/lean && lean Resolution.lean # Lean 4.35, about a second cd ../.. && lake build Composition # Parts II and III together # the 33 vectors: resolution-vectors/vectors.json; the 34 registrar-log cases: resolution-vectors/registrar-logs.json