Skip to content

The agent Genome Project

An authored agent genome: a single seed file, written in a controlled lexicon, that a model unpacks conversationally into a working, consent-first agentic system. The Human Genome Project read a genome no one authored. This project writes one — and watches what it builds.

The durable stamp

Published 2026-07-21: the full seed-1 genome file — the first seed, authored 2026-07-20 — together with its sha256, at stable paths. The file ships verbatim; the hash below is printed here so the artifact and the claim can be checked against each other from this page alone.

  • seed-1.md — the complete genome file, unmodified.
  • seed-1.md.sha256 — the hash line.
  • seed-1.md.ots — OpenTimestamps proof. The anchor was submitted to public calendar servers on 2026-07-21; it becomes independently verifiable (ots verify seed-1.md.ots) once the Bitcoin attestation completes.

sha256 (seed-1.md):

e73e139958ecdebbcfda6781a3bceb78a0c36cbb9e9b01f38e3e23113e08542b

To verify: download the file and run sha256sum seed-1.md — the output must equal the hash above.

What this is

The seed is DNA for a model substrate: a contract file in a controlled lexicon under a ruled syntax, refined generation over generation. The published seed-1 unpacks the founding contract — the two-definition preamble and the pair it teaches. Later seeds added the organs of an operating system: a generated home surface (seed-2), a cross-linked local wiki with telemetry (seed-3), and the unattended refinement loop itself (seed-4) — throughout, a permission model where reach is granted rather than taken, and heredity through the seed cadence. The model is the CPU; the genome is the boot image.

The framing is honest about its limits: this is directed evolution, not blind Darwinism — the variation is authored, and selection is ruled by a human against a rubric. As of 2026-07-21, four seed generations exist (seed-1 through seed-4), and every expression to date has run on the Claude Fable 5 model family. Running instances are observed, never edited; improvement travels only as the next seed.

What is proven

Each item below was observed at bytes in the project record — recorded runs, recomputed digests, scored verdicts.

What is not proven

Unproven means unproven: designed or intended, but never demonstrated.

The failures are part of the record

A development record is credible because it includes its defects. The most recent, as of 2026-07-21: a generation-4 run — the first fully hands-off revolution — failed its own fabrication gate. Its digest rule was self-referential: the run included its own report inside the digest the report attests, so the claimed hash was structurally unreproducible — the independent recompute returned a different value. The mechanism ran perfectly; the claim failed the check. That defect is the next pin: the next seed is slated to pin the digest-scope law instead of leaving it to per-run interpretation.

The artifact is the proof.

Read seed-1.md