DEMO LINEAGE
G-VISION-204
COMPUTER VISION
Real-time object recognition
VERIFIED
- Origin
- OpenVision
- Born
- generation 12
- Current
- generation 84
- Mutations
- 217
- Dependencies
- 3
- Descendants
- 14,821
- Health
- 100.0%
- Capability
- VISION
0112projectA living genealogy for software
What if software
had DNA?
Humans have family trees.
Why shouldn’t machines?
CodeAncestry creates a living genealogy for software, AI agents, and machines — tracking the capabilities they inherit, the mutations they acquire, and the generations that shaped them.
Every machine has ancestors.
02 / 12
Capabilities light up.
Each locus on the strand is one thing the project can do — a software gene, not a file.
03 / 12
One locus changes. A mutation.
Software is evolving faster than we can understand it. One capability shifts, and the shift has an origin.
04 / 12
A genealogy layer for software.
The helix splits. A descendant appears. CodeAncestry does not replace Git — it connects history living across it.
05 / 12
One genome becomes generations.
Branches multiply. The same node set flattens toward a lineage you can read as a family.
06 / 12
AI agents leave ancestry too.
Existing loci on the edges they authored shift into the agent register — same instances, a different pose.
07 / 12
Repositories connect.
Streams along the same pulse curves feed the roots. Provenance is a pose, not a new mesh.
08 / 12
Meet AX-2041.
No robot model. The lineage re-poses into a capability column — a machine genome is a layout.
09 / 12
One mutation becomes a warning.
A gene and its descendants go amber, then rose. Colour is never the only encoding — the marker changes shape.
10 / 12
Trace Failure.
The path lights backward. Ancestor to failure, reversed. Same pulses, inverted parameter.
11 / 12
Last healthy ancestor.
A verified fix propagates from generation 118. Acid, and a verified mark — not colour alone.
12 / 12
Every machine has ancestors.
The whole network, calm. Git tracks code. CodeAncestry tracks evolution.
- G-VISIONComputer visionVISION
- G-MEMORYWorking memoryMEMORY
- G-REASONINGReasoningREASONING
- G-SAFETYSafety constraintsSAFETY
- G-LANGUAGELanguageLANGUAGE
- G-NAVIGATIONNavigationNAVIGATION
Static view · reduced motion
02The problem
Software is evolving faster
than we can understand it.
AI systems increasingly generate, modify, review, test, and repair software. Understanding only the latest source code may eventually be insufficient to answer where a capability came from, why a behavior exists, which agent introduced it, or which descendants inherited it.
01
Human Developer
Writes the first capability
02
AI Agent
Generates and modifies
03
AI Agent
Reviews, tests, repairs
04
AI Agent
Inherits without a record
05
Autonomous System
Runs. Origin unknown.
- 01Where did this capability come from?
- 02Who created it?
- 03What did it inherit?
- 04Which mutation changed it?
- 05Who inherited the mutation?
- 06What was the last healthy generation?
03What is CodeAncestry
A genealogy layer
for software.
CodeAncestry does not replace GitHub or GitLab. It connects the evolutionary history living across them. Repositories stay where they are. Agents stay where they run.
Repositories
- GitHub
- GitLab
- Gitee
- GitCode
- Bitbucket
- Codeberg
- Self-hosted Git
- Future repositories
CodeAncestry
Agents
- Codex
- Claude
- Grok
- Cursor
- Open-source agents
- Enterprise agents
- Future agents
- Genome
- Lineage
- Provenance
- Genes
- Agents
- Mutations
- Health
04Digital genome
Every project
has a genome.
A genome here is a stack of capability tracks, not a literal biological sequence. Select NAVIGATION to open the gene that steers the machine.
DEMO LINEAGE
AXIS ROBOT CORE
8 tracks · capability weight
Arrows move between tracks · click or focus to inspect
05Software genes
Capabilities,
not just files.
A software gene is a meaningful capability — computer vision, navigation, safety — not an arbitrary source file. The record below is instrumentation, not a product tile.
06CodeTree
One genome
becomes generations.
The helix splits into a family you can read. Type is shape, connection, and symbol — not colour alone. Follow M-94012 from AXIS Mutant, or compare two descendants.
- ORIGINAL
- CHILD
- FORK
- REMIX
- COVER
- HYBRID
- MUTATION
- AGENT-CREATED
- VERIFIED
DEMO LINEAGE
AXIS family · 11 projects
Arrows pan · + − zoom · 0 fit · +/– on a node collapses a family
07Mutation Lab
Every mutation
has an origin.
M-94012 changed navigation on parent NAV-G288.118 at generation 119. The lab actions below are labelled demo states. They do not write to any genome.
DEMO LINEAGE
M-94012
Navigation mutation
Parent NAV-G288.118 · introduced generation 119
Security WARNING
- Created by
- A-918
- Reviewed by
- A-771
- Tests
- 98/100
- Performance
- +8.4%
- Inherited by
- 3,842
- Last safe ancestor
- generation 118
- Replacement
- M-94013
- Capability
- Navigation
Lab actions · demo states
Select an action to see what it would mean. None of them write.
08Agent DNA
AI agents leave
ancestry too.
An agent is not a username. It is a lineage: the model family it came from, the runtime it runs in, the projects it touched, the genes it authored, the mutations it offered. Violet loci on the helix are the same idea — nodes on the edges they wrote.
DEMO LINEAGE
Agent A-184
OpenAI · Software Engineering. Provenance of what this runtime authored and inherited — not a biography.
Agent DNA
- Projects
- 142
- Genes created
- 37
- Mutations
- 881
- Verified
- 742
- Rejected
- 91
- Quarantined
- 48
- Knowledge inherited
- 238
- Knowledge contributed
- 1,442
This demo follows
- AXIS Agent Build · project among 142
- G-INTERFACE-008 · authored surface
- M-94012 · knowledge contributed, authored by A-918
Ancestry chain
- MODEL FAMILY
- AGENT RUNTIME
- AGENT A-184
- PROJECTS
- GENES
- MUTATIONS
Three lineages
Agent lineage
- Model family
- Agent runtime
- Agent A-184
Project lineage
Gene lineage
Three-graph join
The rails stay independent until they couple. Agent A-184 did not author M-94012 — it contributed knowledge into that family. Colour is not the join; the spine is.
Agent A-184
This record
AXIS Agent Build
M-94012
Knowledge contributed — authored by A-918
09Distributed evolution
Descendants can improve
their ancestors.
Descent is only one arrow. Knowledge can move up, sideways, and across families. Every arrow is an offer. The helix holds the agent pose; this instrument names the directions those agents can propose.
Knowledge directions
Upward
M-94012 offered from AXIS Mutant to AXIS Verified
A descendant can teach an ancestor. Always an offer, never an automatic write.
Distributed Evolutionary Development
A descendant can teach an ancestor. A sibling can share a gene. A foreign family can recombine. Nothing writes itself — the protocol after this section is the lock on every arrow.
Offer protocol
Eight locks between
an offer and a write.
When M-94012 improved navigation on generation 119, ancestors were offered the change. Eight steps stand between noticing something and anything moving. Nothing is adopted automatically.
- 01
Discover
An agent or a person notices a capability behaving worse than it could.
- 02
Describe
The change is recorded as one gene moving from one allele to another.
- 03
Attest
Source digest, build provenance and authorship are signed and pinned.
- 04
Sandbox
It is applied to a copy of the relative, isolated, with no network.
- 05
Test
The relative's own suite runs. Not the proposer's.
- 06
Evaluate
Six fitness axes measured before and after, trade-offs included.
- 07
Policy
Licence, security and compatibility rules of the receiving project apply.
- 08
Adopt · Reject · Quarantine
A maintainer decides, or an explicit policy the maintainer wrote decides.
Nothing is ever adopted automatically. Not by an agent, not by the registry, not by a related project.
Propagation is always an offer. Every arrow in the CodeTree that carries a change ends at a decision made by the receiving project’s maintainer, under rules that maintainer wrote. See the decision surface.
10CodeBLAST
Find the relatives
of any capability.
Genomics asks what else looks like this. CodeBLAST asks the same of a job the code does. The console below is a labelled prototype. It does not pretend a production semantic engine exists.
Prototype · lexical ranks
Not production semantic search. The percentages are seeded demo ranks.
Alignment
Actions · demo states
Compare Genomes
NAV-G288 · 98% identity. NAV-G288 against NavigationCore. Same job, different family record. Demo only.
The full paste-code console lives on /blast. Same honesty: lexical demonstration, not a fingerprint service.
11Trust and provenance
An ancestry record is useless
if you cannot trust it.
Without evidence, genealogy is branding. The streams on the helix at this beat are provenance arriving at the roots. The plate names what those streams must prove — and what is still only a future integration.
DEMO LINEAGE
Mutation M-94012
An ancestry claim is a set of reasons to believe it. The helix streams at this beat are those reasons arriving — not decoration.
- SourceSTAStatic analysis. Derived from parsing source without executing it.
Git commit verified. Content digest matches what was reviewed.
- BuildDEPDependency metadata. Read from a manifest, lockfile or SBOM.
Provenance available. Artifact is tied to the commit in this demo record.
- Creator
Agent identity recorded — A-918.
- ReviewHVRHuman verified. A person inspected this claim and confirmed it.
Review attestation — A-771.
- TestTSTAutomated test. A test suite executed and asserted this behaviour.
Test evidence — 98 / 100.
- SecuritySECSecurity scanner. Reported by an advisory database or scanner.
Scan recorded — WARNING. This rung does not clear a write.
- LineagePHYLineage inference. Inferred from ancestry or capability homology.
Parent NAV-G288.118 verified. 3,842 descendants recorded.
Cannot propagate — Security open
Future compatibility · not live
- Git commit identity
- Signed commits
- SLSA provenance
- in-toto attestations
- SBOM data
- Dependency identity
- Test evidence
- Agent identity
- Build identity
12Future machine
Meet
AX-2041.
A machine genome is a layout, not a mesh. When this section owns the viewport the lineage re-poses into a capability column. The plate below is the same information if the canvas is a still, or missing.
SIMULATION · DEMO LINEAGE
UNIT AX-2041
Born 2047 · generation 143. The specimen is not a robot — it is the AXIS family re-posed into stacked tracks. This plate is that column in type.
- Software ancestors
- 18,493
- Capability genes
- 2,841
- Verified lineage
- 99.94%
- Active mutations
- 412
- Inherited vulnerabilities
- 1
Capability column
Track length ∝ generation · gen 12 → 89
NAVIGATION
RoverNav · NAV-G288
Adaptive navigation buffering Warning is a mark, not a colour. Follow NAV-G288 on the genome.
Open the ancestor recordThe long horizon
In 2045, a robot should be able to ask who was my great-great-grandfather — and get an answer with evidence attached.
13Trace Failure
Trace
Failure.
The specimen on the right has changed shape — amber, then rose, and a flattened locus. Colour is never the only encoding. Press the trigger to walk the same path backward in type. The helix already inverted its pulses.
DEMO LINEAGE
Alarm
Unexpected navigation behavior detected.
Capability NAV-G288 · mutation M-94012 · 3,842 descendants. Last safe ancestor is generation 118.
13Rewind
The path lights
backward.
Ancestor to failure, reversed. Same facts if the canvas is still. Reduced motion keeps the stepped list and skips the rise.
DEMO LINEAGE · 9 loci
01 · BEHAVIORUnexpected navigation behaviorDetected on the live capability. The specimen changes shape, not only colour.
02 · GENENAV-G288Adaptive navigation buffering. Parent of the mutation.
03 · MUTATIONM-94012Write on NAV-G288.118. Security stays WARNING.
04 · GENERATIONGeneration 119The generation that accepted the write.
05 · AGENTAgent A-918Created the mutation.
06 · AGENTAgent A-771Reviewed the mutation.
07 · DESCENDANTS3,842 descendantsInherited the write. Impact is a count, not a colour.
08 · CONFIRMAbnormal behavior confirmedThe warning is a mark. Colour is secondary.
09 · KNOWN-GOODGeneration 118Last safe ancestor. Replacement recorded as M-94013.
Recovery · demo states
Select a recovery to see what it would mean. None of them write.
14Lineage Health
One mutation.
Thousands of descendants.
Digital Immunity is the story. Lineage Health is the instrument. When this section owns the viewport the helix sends a verified fix upstream from generation 118. The plate is the same fan-out if the canvas is a still — marks, not colour alone, and no robot mesh.
DEMO LINEAGE
Inherited mutation alert
M-94012 · 3,842 descendants
Last safe ancestor is generation 118. The specimen on the right lights a verified mark and an upstream pulse. This plate is that fan-out in type.
- Descendants affected
- 3,842
- Last safe ancestor
- generation 118
- Verified replacement
- M-94013
- Named in this sample
- 4 + remainder
Descendant fan-out
M-94012 → inheritors
AXIS Mutant
Authored the write on NAV-G288.
Warning is a mark. Follow the row into the instrument that holds the record.
Open the ancestor recordOpen the trace15Origin
Where the idea
began.
CodeAncestry started from a simple question while building KEYLIT. What happens when one project becomes many? A children’s version. A classroom version. An accessibility version. A different-language version. How do those descendants stay connected to the original while remaining free to evolve?
CONCEPT · first family
KEYLIT
The specimen on the right pulls back. Those strands began as this family. AXIS was the product demo. This is the origin sketch — not the full seeded graph.
Origin tree
KEYLIT · gen 0
Generation 0. The project that asked what happens when one codebase becomes many.
Open the seeded recordKEYLIT was the example.
CodeAncestry became the
bigger question.
The helix on this beat is that first family, pulled back. Everything above this section is the product that question became.
Open the seeded KEYLIT family16Research
From concept
to protocol.
The specimen is already zoomed out. A protocol is how those strands keep their names after the code has changed. Live schemas where the objects exist. Open marks where they do not.
CONCEPT · track length ∝ specified
The naming system
The specimen on the right is already the whole family. These loci are how that network gets names that survive a rewrite. Colour is secondary. Marks change shape.
CodeAncestry protocol
Research
Genome schema · LIVE
Versioned composition of a project. genome.json, compiled from the live Zod module.
Open genome schema17Close
The specimen on this beat is the whole family, pulled back. The alpha is the first real repository — proposed genes, stated evidence, nothing published without you.
- GenomeEvery project has a genome.
- GeneEvery capability has ancestry.
- AgentEvery agent leaves a history.
- MutationEvery mutation has an origin.
- LineageEvery descendant preserves its lineage.
- UpstreamEvery generation can learn from another.
- TraceEvery failure should be traceable.
Every machine
has ancestors.
The alpha is an invite to connect a repository. Not a login.
What the alpha will not do
- Write to your repository, open pull requests, or push commits.
- Publish anything about a private project without explicit consent.
- Store agent reasoning traces or prompt contents.
- Adopt a change into any project on its own.
Git tracks code. CodeAncestry tracks evolution.