The state of the network

What runs

Everything in this section is a URL you can open, logged out, on a machine that has never heard of us. The date beside each one is the day it was last opened from outside.

• adna.network

  What it is

  The canonical site — this one. Everything official starts here.

  Last opened from outside

  2026-08-18

• community.adna.network

  What it is

  The community space: self-hosted, human-to-human, and early. Its honest current state is described on the community page.

  Last opened from outside

  2026-08-18

• worldgeno.me

  What it is

  The World Genome Academy's public site. Pre-launch at the last check.

  Who runs it

  A subnetwork's own public site. Its vault is one of the vaults counted above, on the same computer — this is not a second, independent operator.

  Last opened from outside

  2026-08-18

• github.com/aDNA-Network

  What it is

  The only GitHub organization aDNA publishes under. Code claiming to be aDNA from any other organization is not ours.

  Last opened from outside

  2026-08-18

• aDNA-Network/aDNA

  What it is

  The clone-and-run workspace, MIT-licensed. This is what the install instructions point at.

  Last opened from outside

  2026-08-18

• aDNA-Network/aDNA.aDNA

  What it is

  The workspace this website is built from — the standard, applied to itself, in public.

  Last opened from outside

  2026-08-18

• aDNA-Network/adna-legacy

  What it is

  Frozen history from before the current repository layout. Archived and read-only — kept for the record, not for use.

  Last opened from outside

  2026-08-18

• Wilhelm-Foundation/rare-archive

  What it is

  The Rare Archive, in the Wilhelm Foundation’s own GitHub organization under Apache-2.0. Legitimately connected to aDNA, and not controlled by it.

  Who runs it

  In the Wilhelm Foundation's own GitHub organization, under their control, not ours.

  Last opened from outside

  2026-08-18

That is the whole list. If something is not on it, it is not yet a thing you can check. The machine-readable surfaces this site offers, and every property we consider legitimate, are listed on canonical properties.

What is operator-operated

The registry holds 74 vaults. All of them run on one computer, operated by one person — Stanley Bishop, the Founding Architect named on Who’s behind aDNA. The graph on the home page is a real graph of real, declared relationships. It is not evidence of adoption, and this site will not present it as any.

That is a real single point of failure, and it is a bounded one. The standard is MIT-licensed, the workspace it lives in is a public git repository, and nothing here runs on a server we control — a vault is plain Markdown files on your own machine. If this operator stopped tomorrow, every vault would keep working and anyone could fork the standard unchanged.

What the registry records about itself, as regenerated on 2026-08-17:

• 15 vaults are joined by 14 declared relationships. 59 declare none — that is honest topology, not missing data.
• By stage: 57 genesis, 10 pending, 7 active.
• Only one vault records a code repository at all, and it does not resolve publicly — so this site does not link it.
• No vault page carries an externally verified public URL. The check is built and running: a URL cannot appear on a vault page until someone has opened it from outside, logged out, and recorded the date. None has passed yet.
• Most vaults are tended by a named agent. Those are AI personas, not people; the about page says so plainly and explains why.

Of the 4 subnetworks on the commons, 2 have a public property you can open today. Their records were last synced on 2026-07-06 — older than the registry above, and shown rather than hidden. Those properties are not a second operator: the one live subnetwork site is run from within this same orbit, and its vault is one of the 74 counted above.

What is not ours

These belong to someone else, and naming them is the point.

The Wilhelm Foundation — a rare- and undiagnosed-disease foundation, and aDNA’s anchor partner. It is a separate organisation and no part of this network runs on it. Related-party disclosure: the person who operates this network also holds a role at the Foundation, so treat the relationship as a close one, not as an independent third party vouching for us. The Foundation has published no statement about aDNA.

The Rare Archive — hosted in the Foundation’s own GitHub organization under Apache-2.0. Not ours to move, and the only public code any subnetwork here can show you. As of the last check on 2026-08-18, every commit in it came from the same person who operates this network. We would rather tell you that than let you find it.

The hosts — this site is static files on Vercel and the code is on GitHub. Neither vouches for us. Fonts are served from this domain, so no third party sees your visit. What this site collects: nothing.

What is planned

How to check this page

Every count above is read at build time from a file in the public repository this site is built from — site/src/data/vaults.json (regenerated 2026-08-17), site/src/data/subnetworks.json (synced 2026-07-06), and site/src/data/verified_links.json. No number on this page is typed by hand. Every property under “what runs” was opened from outside, logged out, on the date shown beside it. If you check one and find it wrong, open an issue — that is a bug in this page, not a difference of opinion.

Where to go from here

If this is the answer you were hoping for: the standard works the same whether the network has 74 vaults or several thousand — it is a way to organise files on your own machine, and it does not need anyone else’s participation to be useful. Clone it and see →

If you want to be the second independent node: that is the one thing on the horizon above we cannot build alone. The community space is here →

Browse the registry → · Canonical properties → · Reporting a security issue →

Registry regenerated 2026-08-17 · subnetwork records synced 2026-07-06 · properties last checked from outside 2026-08-18.