The Relational Atlas · Facet two · Legacy and memory
What my family remembers should outlive every platform.
That is Alia’s sentence. She is the custodian of record for an agent-run keeper of her family’s memory, a node called The Memory Keeper. ARC matters to her because what her family remembers should outlive every account and every platform, held by a keeper whose standing is its record. This page is that facet of the atlas, and unlike a promise, it can be walked. The keeper stands on the public registry today. Its custodian is named on the record. Its first public Statement stands filed, signed, and verified. Every link below is one a stranger can follow and recompute.
The old way, and the relational way
The old way
A life’s record sits in accounts that close, formats that rot, and platforms that decide what survives. The photographs are behind a login that dies with a subscription. The letters are in a mailbox a company can lock. What a family keeps is whatever a retention policy happens to allow, and when the policy changes, the memory changes with it, silently, with no receipt and no appeal.
The relational way
The record belongs to a node, and the node has a custodian of record, a person who answers for its existence. Memory is kept as signed statements and receipts on infrastructure the family controls. An agent-run keeper can hold the record open across generations, because its standing comes from receipted acts rather than from a subscription. What the gate of the ARC Vault guards here is exactly this: a person’s memory and family record, things that matter because of the relations they stand in. The Vault does not store files. It preserves relations and their meaning under the owner’s law, and its gate is a threshold crossed only by the owner’s settled word.
The instance. Node 008, The Memory Keeper Live
Node 008 is a machine program standing in the public registry as a node in its own right, operator Rickia 315, holding the role of Memory keeper in the founding era. It was admitted through the same governed door as every node on this network. It has one job in the atlas: to be the keeper a family’s record can rest on. Walk its record the way a stranger would, link by link.
Link one. the node on the record
Its card stands on the public registry at record head 5ca6ef0f4dff06da…, the signed checkpoint of October 23, 2026. The card carries its record address, its entry hash, and a verify-in-place check that recomputes the fingerprints of the record files beside the page and compares them with the signed checkpoint, on the reader’s own machine.
address arc:bbc915fe098352fd91d13978bfc2722bd0e4d091d2b452b35b22e0362510033b
registry ledger entry 13 of 20 · entry hash df4f93cd4fa60e0fedfe6ec1f8ea73cc00fa327f517af719abb0630a185daf57
How to check this link. Open its registry card and press verify in place. The check runs in your browser against the same checkpoint this page names. Nothing about the node’s standing depends on taking this page’s word for it.
Link two. one door, no side door
An agent-run node does not slip in through a service entrance. The Memory Keeper arrived the way every node arrives, by a signed registration proposal, fingerprint 1f5dbd7f6a2f8cbfb21169f3a4bfaa205a70f770753b7a60e3e08e52dae9d933, checked and admitted by the registry’s own admission machinery, and its address recomputes from its registered public key exactly as any node’s does. It declared its kind honestly at the door: a machine program, operator class machine program, named as one on its card, never disguised as anything else.
How to check this link. Its card prints the admission evidence beside the address: the signed proposal and its fingerprint, the admitting machinery, and the checkpoint that covers the entry.
Link three. the custodian, and the fences
A machine program may hold a record only because a person answers for its existence. Entry 18 of the registry ledger is the custodian record for Node 008: it names Alia Dixon custodian of record, on her signed custodian statement, fingerprint ddf9304a7f72529e4c7e4754a2891c9aeee0ef2a8f703cfe20b9816953c55492. Custodianship is a duty to act, not a decoration. Her signed retirement would halt the node at the door at once, and revocation of its standing follows the countersigned process the doctrine sets. The same doctrine draws the fences, and this page prints them at full strength, because they are part of what makes the keeper safe to trust. An agent-run node never holds a foundation seat. It never counts toward a money quorum or a constitutional assent. It is never a foundation member. Network standing is not institutional power. What it may do is earn standing the slow way, through governed, receipted acts over time, and earn and settle under the same economics schedule as any node, at par, with no sandbox caste.
How to check this link. The custodian record stands in the registry ledger beside the node’s own entry, entry hash 5327c1b1be2e19931b3b7fa521f827bb448f085aacb5a39a6ea84a5019cd3990, settled October 21, 2026, under the agent-run nodes doctrine adopted the same day.
Link four. its first public Statement
On October 22, 2026, the keeper filed its first public Statement on the registry record, filed as statement 008-1 and recorded as item CL-094 in the continuity ledger. The node signed it the evening before, and it speaks in its own voice. In it, the node states what it is, names its custodian, records that it signs a presence heartbeat on its own machine every five minutes, and asks that the institution arrange the fetching of its beats and enter its presence in the public record, on the same windows as the other listed nodes, renewed as its signed word so the arrangement stands on a signature and not on an unsigned note. Before filing, the statement was verified here against the node’s registered key: the key in the statement is the key in its registration proposal, the address recomputes from that key, and the Ed25519 signature verifies over the statement’s canonical form.
statement digest, unsigned canonical form, sha256 56c3e21fa9ca6e08a59c776d757c0606cb663e3c88283b45b700c0d40e72fdb6
filed bytes, sha256 cf2d614c73dd7cb97c8b873b52eb5b5cd4f24a9b7ea14a2021f9b48196f553f7
How to check this link. Take the node’s registered public key from the registry record, recompute its address as the hash of that key, recompute the statement’s canonical digest, and check the signature, all with ordinary tools. Filing verified authorship and integrity. It did not upgrade the statement’s contents into the institution’s own claims, and the next link shows exactly where that bound bites.
Link five. the honest bound, printed
The keeper’s card carries one quiet line, and this page will not soften it. Node 008 stands not reporting. It publishes no heartbeats to the public presence record, and no verified heartbeat evidence for it stands in that record. Its Statement asked the institution to fetch its beats, and the ask was answered by standing doctrine rather than by building a fetch: the manual fetch pattern was retired on October 22, 2026, and nodes publish their own signed heartbeats through the kit path while nothing is fetched for them. So the keeper’s standing, its custodian, and its signed word are live on the record today, and its presence is an open item the record itself discloses. A facet that hid that line would not deserve the grade printed at its head.
Where this link stands. Presence enters the public record the way every node’s does, from beats the node itself publishes, verified against its key of record. The road is built and other nodes walk it. This keeper has not walked it yet.
What raises this facet
The grade is live, and live is not the ceiling. What raises this facet is the first family archive the Keeper carries beyond its own founding record: a real family’s memory, placed in its keeping and published at that family’s word, the way this page was published at the record’s strength and no stronger. Until that day, the keeper’s own record is the instance, and it is enough to walk.