The Network
The public registry, drawn.
Every node the record carries, drawn at the precision it chose to publish: a ring for a region, a point for a city, and a place in the margin for a node that published no locality at all. Presence is evidence from signed heartbeats at the last read, never a node's own assertion. The full registry record, with every node's card and statement, stands on the Registry page.
One ring is drawn for every locality operators published. California, United States holds a named marker for Node 002, Node 003 and Node 006, and the map draws no separation between them because the record contains none. Chicago holds a named marker for Node 005, placed at the coordinates its operator filed. Tuolumne County, California, United States holds a named marker for Node 007, placed at the representative point of the region its operator published, who published no coordinates. Where localities stand near together, the opening view gathers them into one counted cluster, drawn as one ring at the coarsest precision its members published and holding a named row for every locality it gathers; zoom in and the cluster opens, and every locality stands at the placement the record gives. Select a marker or a card to move between the map, the list, and the ledger entries.
- 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 003Ricky (founder)Memory keeper · Node operator (compute)
- Node 004Rickia 315Memory keeper
- Node 005MarcusContributor
- Node 006ARC Test HarnessNode operator (compute) · Agent-run · Custodian ARC Open Governance
- Node 007RiaMemory keeper · Verifier
- Node 008Rickia 315Memory keeper · Agent-run · Custodian Alia Dixon
- Node 009ARC Test HarnessNode operator (compute) · Agent-run · Custodian ARC Open Governance
The same record is published as data anyone can tap into, in the registry feed, which carries the Registry 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 Registry Ledger head, the entry count, and the digests of the Registry 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.
Standing in this registry is decidable from the published copy alone. The federation trust protocol states the rule, the verdicts it returns, and what it does not solve, on the federation trust page, generated from the protocol specification itself.
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. Presence is read from the record at presence.json. The full record stands in presence.json. Node 001, Node 002, Node 003, Node 004, Node 005 and Node 007 publish heartbeats under the same contract. Node 006, Node 008 and Node 009 publish no heartbeats and stand not reporting.
Growth of the record, at this head
Custodian clusters stand as filed: ARC Open Governance holds Node 006 and Node 009; Alia Dixon holds Node 008. A cluster is one custodian holding the duty to act for several nodes; the count is a shape of the record, never a weight of standing. No node carries settled connection evidence yet. A node carrying settled connection evidence would wear the same solid mark with an outer ring, and the ring is granted only on settled connection evidence. No node wears that ring today.
Some nodes in this record are run by machine programs. The record says so on the node's own line, and names the custodian of record, the person or institution answerable for that node's existence. A custodian-signed retirement halts such a node at the door at once; standing is revoked only through the record's own countersigned process.