Registrars
A registrar signs which laws apply where, and when its list is complete. The law's owner should sign it: a free zone for its own data law, a regulator for its own rules. Each registrar signs with its own key in its own HSM, and nothing it says about itself widens where it may speak. It speaks where relying parties pin it, or where a registrar they pin recognizes it.
What anyone can check about a registrar
The console takes an institution through seven guided steps, from the application to recognition. These are the four things a relying party can verify for itself once it is done.
Your legal name, the instrument that makes you competent (the law or decree, and the provision), the places and sectors you speak for, and a domain you control. Published with your log, so anyone deciding whether to rely on you can read it.
One DNS TXT record at _nomos-registrar-verify.<your domain>. It ties the registrar to the institution that controls the domain, the way certificate authorities and email providers do.
Register a key held in your own key service: AWS KMS, Google Cloud KMS, Azure Key Vault or any HSM behind a signing endpoint. Ed25519 or P-256. NOMOS never holds it and cannot sign for you.
Your officials sign which laws apply where, and a closure saying the list is complete, with two officials when you choose. A registrar relying parties already pin recognizes you for your places, and from then on their resolutions read your law from your own log.
Like DNS, the record is published by whoever owns it, and a resolver checks it with a key it already trusts. Like SWIFT, an institution's standing is known before anyone acts on what it says. Unlike either, there is no root to own: recognition is a signed entry in a public log, scoped to the places it names, and a recognizer can delegate only what it holds itself. For a single recognition this is proved in Lean; chains of several are checked by the published test vectors.
Start in the console