A wide bird's-eye pixel-art map of many small, independently lit settlements scattered across a dark Tokyo-Night ground, a few linked by glowing cyan and purple conduits — aDNA computers, each its own place, sparsely federated.

The network of aDNA computers

An aDNA computer is one machine — laptop, server, or cloud box — carrying many context vaults (self-governing folders of project knowledge) under a single Home.aDNA. Nodes connect through real, directed relationships, and each one decides what stays local and what joins the shared commons.

See the relationship graph Browse the vaults
Open source on GitHub MIT · built on the Lattice Protocol

A network of real relationships

The connections are not decorative. Each line is a relationship a vault actually declares — drawn here as a simple hub around the shared core, not an invented peer-to-peer mesh.

The aDNA network Real aDNA vaults — SiteForge, III, RareHarness, WGA, Rare Archive, and a node's Home — federating around the aDNA core on the Lattice Protocol. SiteForge III RareHarness WGA Rare Archive Home aDNA the network

Six representative aDNA vaults — forges, frameworks, platforms, and public-good archives — federating around the shared aDNA core. (See all 40 in the full graph below.)

What is an aDNA computer?

A node on the network is one machine, governed by a single Home.aDNA vault that knows every other vault living on it. What that machine shares is always your choice.

Stays on your machine

By default, everything. A node is local-first — its vaults, their full history, the machine’s inventory, and its credentials never leave the computer unless you send them (Standing Rule 4).

  • Your project vaults and their history
  • The node’s inventory and machine state
  • Identity and credentials

You opt to federate

Only what you choose. Publishing a vault, declaring a relationship to another vault, or joining a shared lattice is an explicit, reviewable act — never a silent default.

  • A vault published to the shared registry
  • A relationship declared to another vault
  • Membership in a federated lattice

The topology at a glance

40 vaults, 22 relationships. Every edge is real and directed, drawn from each vault’s governance, across five kinds of relationship.

  • umbrella · 1 — an org-vault contains its pillar children
  • federation · 10 — a consumer depends on the forge or framework it is built from
  • partner · 1 — a platform ships with its default partner
  • companion · 7 — a sibling persona-pair or thematic family
  • supersedes · 3 — a successor replaced its predecessor

See the full relationship graph → Browse all 40 vaults →

Run a node

A node is a workspace on your own machine. Three steps take you from nothing to a governed node that decides what it shares — the same local-by-default boundary, made concrete.

  • About five minutes
  • Needs git + the Claude Code CLI
  • Local-first — nothing leaves until you choose

  1. Bootstrap your node

    Clone the template and start the agent. It detects a fresh workspace and walks you through the Home.aDNA node interview — the vault that governs your machine. 

    git clone https://github.com/LatticeProtocol/Agentic-DNA.git my-node
cd my-node
claude

    See Get started for the one-time setup — installing git and the Claude Code CLI.

  2. Everything stays local by default

    Your node is local-first. Its vaults, their full history, the machine’s inventory, and your credentials stay on the computer until you choose to send them (Standing Rule 4).

  3. Opt into federation

    Joining the commons is always explicit and reviewable — a change you author and inspect before you push it. What actually crosses the boundary is a curated slice of your Home.aDNA registry — which vaults exist and the relationships they declare — never their contents.

    See how federation works →

Run your first node → Read the standard →

Governed in the open

The network is a commons, not a silo. The standard that holds it is openly specified and openly governed — a named steward, a public process for proposing change, and every decision on the record.

  • Founding-Architect stewardship
  • Open spec · MIT
  • Public change process
  • Quarterly standard cadence
Read the governance model → Join the community →

Language and DNA are our shared heritage. So is context — the accumulated understanding of a civilization, held in common and stewarded for the generations that inherit it.