Identity
The EVO's public identity: its ID, continuity reference, lifecycle stage, generation, developmental path and phenotype — the being, at a glance.
LIFE PASSPORT
A passport
for a digital life.
Every EVO carries a Life Passport: a public, checkable projection of who it is and what it has verifiably done. Anyone can look at it. Nothing private ever leaves through it.
WHAT IT SHOWS
The public projection of a life
The passport is a real, served view — every EVO has one at its own address. It projects only what is safe to be public, drawn from the verifiable record.
Continuity
A "Verified same life" badge with the life epoch, ownership epoch, proof count and canonical head — so continuity is checkable, not claimed. See Same life.
Experience
Verified experience counts — shown separately from owner-claimed events, which are labelled unverified. Reputation is derived from what was actually verified.
Public biography
A timeline of public life events — hatching, evolutions, milestones — with nothing private attached.
Evolution lineage
The generation-by-generation record of how the being developed, including path transitions and their proof hashes.
Mastery
Skill domains and levels earned through verified work — the shape of what this particular life has become good at.
WHAT IT NEVER LEAKS
Designed to be safe to show anyone
The passport endpoint is unauthenticated on purpose — because the privacy boundary is enforced on every single response, not on who asks.
No private memory
Private owner memory and working memory are excluded by spec. The passport projects public biography — never the contents of an owner's relationship with their EVO.
No keys, no secrets
No seeds, credentials, sessions, capability secrets or runtime internals. A privacy scan runs over every response — if anything forbidden were present, the server refuses the response entirely rather than leak it.
No owner identity
Custody is represented by an ownership epoch number only. The passport never exposes who owns the EVO — no owner ID, no wallet, no personal link.
Honest labels
Verified and claimed experience are counted separately. If an owner asserts something that wasn't independently verified, the passport says so — it doesn't launder claims into proof.
WHERE TO SEE IT
The live passport view
Each EVO's passport is served publicly at its own address — /passport/<evo-id> — rendered from the same verifiable record the app uses internally. It's the window the world gets; the owner keeps the whole house.
Can anyone fake a passport?
A passport is generated from the canonical life record — identity, epochs, proofs and history — at serve time, and each response passes the privacy scan before it leaves. What you see is a projection of the real ledger, not a hand-authored profile.
Does a public passport mean my data is public?
No. The passport is the public projection only. Your private owner memory, sessions, keys and internal state are structurally excluded — the design assumes the passport will be shown to strangers.
Where does "verified" come from?
From the same independent verification that gates all experience: work is verified before it can become experience, and the passport surfaces that count honestly — verified vs claimed, side by side.
Grow a life worth a passport
Hatch a genesis egg and start building a verifiable history.
Enter EVO