Rendering
A render studio is coming to this page. Pick a specimen, pick an AI image model, and it draws the creature live from the plate's genes, ready to mint as a creature token in stage two.
One Genome, Many Readings
Every render differs.
The published transcription guide turns the visible genes into a prompt any image model can follow. No render is official, and none ever will be, so the question of what a genome really looks like stays permanently open, and every specimen gets more beautiful as image models improve. Here is the whole pipeline, walked through on specimen № 0043.
01 · start from the plate
Everything begins with the genotype. № 0043 reads clash harmony, seven shapes, asymmetric, and a sine pattern, straight off the plate. No hidden metadata exists, so anyone holding the plate holds the complete genome.
02 · the transcription is the prompt
The guide converts the visible genes into a prompt, mechanically. This is the actual transcription of № 0043, generated by the published rules with nothing hand-written.
03 · pick a model, get a creature
Hand the prompt to any image model, and each one reads the same genes its own way. Switch between three readings of № 0043 below. In the render studio this happens live, on any specimen, with any model.
04 · mint it as a creature token
In stage two, the render you like mints as a creature token. The token records its parent plate, the model, and the guide edition, carries a SOUL.md, and every mint pays the plate's holder, at a price the holder sets.
The genes ride along as attributes, so a creature token is filterable by harmony, symmetry, and every other trait of its parent genome. Paratypes are unlimited per specimen, and none ever becomes official.
Souls
Mint the creature, and its soul comes with it.
Each creature token carries a SOUL.md, an on-chain text file that derives the specimen's temperament from its genes and records who minted the plate and who created the soul, plus one dedication line from its creator. An agent harness loads the file as its persona, so the creature is an agent that transfers with the token, and the file itself explains how to trace its keeper and custody from the chain. Bred children carry bred souls. A clash soul argues, and a glitch soul is unstable on purpose.
The paratype layer is permissionless by design. Fork the contract, deploy your own on the same genomes, or write a new guide that expresses the collection as something we never planned.
The Field Guide Is Unwritten
The mechanics are fixed and published.
The transcription guide is one reading of the genes, and it holds no special authority. Anyone can publish a new set of rules that expresses the same specimens through AI as something else entirely, a different creature style, a soundscape, an architecture, a game character. The genes stay fixed while the readings multiply.
- 01The genotype spec, transcription guide, breeding rule, and studbook are published as plain text that anyone can compute by hand or fork.
- 02No canonical render will ever exist, so the question of what a clashing, asymmetric, 7-shape genome really looks like stays permanently open.
- 03Every token gets more beautiful as image models improve, because the genome stays fixed and new expressions of it keep arriving.