ARC Open GovernanceARC Network
The registry
The registry is the public record of the ARC Network. A node does not join by surrendering its authority to the network. It joins by making its authority legible to the network, through a registration that is itself a governed act, proposed in the open, settled, and entered with the ledger reference that admitted it. A node appears here only when its registration has settled, so every line of this page can be checked against the record in the founding release, network/NODES.md.
The map draws a point only where an operator chose to publish a locality, at the precision they chose. A node that published none is counted in the registry and drawn nowhere. Tap a point to see the node.
- Node 001ARC Open Governance, the institution itselfSteward · Settler · Witness, genesis-era form · Memory keeper · admitted by the genesis entry
- Node 002Ricky (founder)Memory keeper · Node operator (compute)
- Node 003Rickys-MacBook-ProMemory keeper · Node operator (compute)
The same record is published as data anyone can tap into, in the registry feed, which carries the ledger head hash and every settled entry, and in a field projection that any field database can ingest as relations.
Every publication of this record ends with a signed checkpoint, one statement binding the ledger head, the entry count, and the digests of the ledger, the feed, and this registry as published. The checkpoint stands in registry-checkpoint.json and verifies against the registry checkpoint key, a dedicated key whose public half lives here. Anyone mirroring the feed can recompute the digests and check the signature, and a mirror that has diverged fails that check in the open. The field kit carries the verifier.
Presence is published from evidence. A node that heartbeats signs each beat with its registry key, the beats are verified against the key in its stored proposal, and the state shown here is derived from the verified record, never from a node's own assertion. Node 002 stands unknown until the first verified beat is read. The full record stands in presence.json. Node 002 is the only node publishing heartbeats at the founding opening, and every other node stands unknown until it joins the same contract.
Every settled node
Node 001 · ARC Open Governance
arc:5ab0ba3a4b296e33f264a0ceda9633e1fc108c205e8b1fcfb521194678d33a30
Steward · Settler · Witness, genesis-era form · Memory keeper
Genesis
ledger/entry-0000-genesis.json
None published in the founding snapshot
Node 002 · Ricky (founder)
arc:0014bd63ed0abcbb5422e7dfd970f83bfd77e4d3507e61cb6b1942d5f45c4f00
Memory keeper · Node operator (compute)
Founding
registry-ledger entry 002
None published
California, United States (region)
listed
How a node joins
Registration begins with a proposal in the open. The node states its public address, the roles it will play, and the authority it stands on, and the registration settles through the same governed lifecycle as every other consequence on the network. When settlement completes, the listing appears here with its number, its era, and the ledger entry that admitted it. Nodes then meet by signed handshake, through discovery, signed capability advertisement, version and suite negotiation, identity and key-revocation checks, and explicit trust-policy acceptance. Discovery alone never admits authority.
Status, plainly. The registry opens with the founding release. Three nodes are settled, this institution, Node 002, a founder-operated device, and Node 003, a second founder-operated device, and the next line of the registry, Node 004, is open to the first independent operator. A registration is an authentic milestone and not yet a demonstration of independent federation, and this page does not present it as one. The full account of the network at v0.1 stands in NETWORK.md, and the six roles a node can play are set out on the network section of the main page.