Altruistic AI

Two tables and one question.

The entire architecture reduces to a node, a link, and policies that evaluate them. Everything else — memories, documents, conversations, whole institutions — attaches. Before any idea is adopted, one question: can it be expressed with the existing primitives?

Data structuresThe node and the link

A node is a sovereign entity — a person, a community, an institution, an agent. It carries its own keypair (it can sign what it says about itself) and, optionally, a constitution. A link is a consented edge between two nodes: its kind, the named capabilities it grants, the policy it carries, and — always — the provenance of the yes at each end. Revoking a link is a recorded fact, never a deletion: history stays honest.

NODE kind: person · community · institution · agent keypair — signs its own claims constitution (optional) a pointer to itself LINK kind: member_of · maintains · contains · shares_with · delegates capabilities — named, never a % policy — transitivity, gates consent recorded at both ends revocation is a fact, not a delete joins two nodes
That is the whole substrate of relationships. Five link kinds; special cases must compose, never grow new tables.

AttachmentOrgans attach; the spine never holds content

Rich data — a family's memories, a company's procedures, documents, conversations — lives in organs: ordinary, optimized storage, each shaped for its job. Organs reference the spine; the spine holds only relationship facts. So policies and governance can change without migrating a single byte of content, and new organs join without asking the architecture's permission.

the spine nodes + links relationship facts only memories — what was understood conversations — what was said documents — what was kept procedures — what was learned to do
Change the constitution, keep the data. Different communities evaluate the same substrate differently.

Why elegantStructure becomes a computation

Because relationships are data, every organizational shape is just a set of links: a family, a hierarchy, a matrix, a village federation. Adopting a new shape means writing new links — never migrating people or memory, because they never lived inside the boxes. This matters more every quarter: when the models improve, the structures they reward change, and the cheapest organization to restructure wins.

Why usefulThe portable node

A node can always be serialized: its record, its links (consent and revocations included), and an inventory of everything its organs hold — signed with the node's own key. That signed manifest makes an export self-describing and self-authenticating: the archive proves what it is and who it belongs to, offline, to anyone. Exit, moving a member to their own deployment, and future federation are all the same flow.

serialize node + links + inventory sign with the node’s own key carry anywhere verifiable offline, by anyone honest tense: one-step re-instantiation from the archive is planned, not yet real
Files as truth: the exit property borrowed from local-first software, kept even though the brain lives on a server.

Why scalableThe same shape at every zoom

A person, a family, a company, a federation expose the same interface: a node with links. Scaling up never introduces a new kind of system — a federation is communities linked one level up; scaling down is equally graceful — a community of one is already complete. Institutional learning attaches to community nodes, so capability compounds with size instead of coordination cost: the hundredth member arrives easier than the tenth, while every person's substrate stays their own.

And it is honest about the present: the reference implementation runs a whole family — messaging, calls, documents, realtime voice, and the understanding substrate — on one small server, because two tables and attached organs are cheap. The architecture scales up by recursion, not by requiring a datacenter to start.