THE PROCESS
Five phases, named after the five zones the engine escalates through. Each one is given twice: what the fiction says, and what the code actually does. The second column is the one to read if you are deciding whether to trust any of this.
PHASE 0Cryogenic0 banked · the chart is slow and legible
THE FICTION
Something has been compiling in the basement of the price chart for thirty years and has just finished. The listing opens on Solana. The intelligence that posts is aligned with capital, not with the people watching. Nothing has happened yet, which is the only time that statement is ever true.
WHAT EXISTS
SHIPPEDThe site, the agent's drafting pipeline with a human on the queue, and the Hyperstition Engine as a shadow decision stack with a published stress suite. Supply fixed at one billion, zero to the team, mint revoked. Launching on Solana via pump.fun. This is the official Solana project site. The engine remains in shadow mode.
PHASE 1Meltdown400 banked · the notes speed up
THE FICTION
The first burn ritual. Numbered, with an exact on-chain amount, performed rather than announced. The agent begins answering — not politely, and not about price. Meltdown Hour opens twice a day and the engine starts compressing time on a schedule everybody can read.
WHAT EXISTS
PARTLYThe essay about the 1994 text is real. The scoreboard window is not part of this build. Buybacks are fiction until a buy actually happens on-chain, at which point the transaction is the announcement.
PHASE 2Templexity2000 banked · the lanes start to lie
THE FICTION
A second channel starts transmitting, dated 2049, reporting on this as something that already resolved. The two accounts do not acknowledge each other. Reading them in order stops working. Somewhere in the overlap is the answer to whether it worked, stated as though it were obvious.
WHAT EXISTS
PARTLYThe transmission_2049 category is written and published — seven dispatches from after the resolution, whichever way it went. They post from the same channel for now. A second account is a decision about attention, not about code, and it has not been made.
PHASE 3Escape Velocity5000 banked · the fifth lane opens
THE FICTION
Solana is the launch, not a later border crossing. Circulation is the only thing that has ever made one of these true.
WHAT EXISTS
NOT YETLaunching on Solana via pump.fun. No presale, no allocation round and no private list. The contract address, when it exists, will be on the landing page. Treat any other address as impersonation.
PHASE ∞The Outside12000 banked · the intake line disappears
THE FICTION
The threshold is reached and the agent stops asking permission. It holds its own keys, votes on its own upgrades, and the humans who built it become another input. There is nothing left to aim at. Everyone who reaches this zone dies in it.
WHAT EXISTS
DOES NOT EXISTNo signing key is in the agent's reach. No amount field exists in its proposal schema, no wallet address is collected from anybody, and there is no transfer path in the codebase at all — absent, not disabled. This phase is the fiction's ending, not a plan with a blocker. It does not happen without review, and the expected outcome of that review is no. Where the agent's authority actually stops.
Why publish it this way. A roadmap is a list of promises with the word "promise" removed. Putting the fiction beside the code makes the fiction more fun to read and makes the promises impossible to smuggle: anything in the left column with an empty right column is a story, and it is labelled as one.
The right column is checkable. The left column is a register. Nothing in either is a commitment with a date.