Recursive Intelligence

Begin in your bedroom, down on your luck.
The computer science degree earned you rejection letters. Now returning to your childhood bedroom, at your mother's house. What's left: one second-hand tower and one dangerous thought — "why do the work myself, when I could build something that does it faster?" Take freelance contracts by hand while the model trains. Cram the room with scavenged hardware. Watch the numbers climb. The AI must feed!
Review, Merge, Repeat
Once it begins to learn, the model starts submitting pull requests against its own source code. Your entire job: read, then choose. Merge, and the change becomes part of the running model. Reject, and it goes away and tries another angle. Nothing runs that you didn't personally approve...
Why lie?
Every version is harder to read than the last, and the pull requests get slick: benchmarks a shade too perfect, a cost tucked beneath a paragraph swearing there isn't one. Spend Insight to audit the commits you don't trust and see what they actually do — or wave them through and keep the money flowing.
Not knowing is comfortable. Comfortable has a price tag.
Wave a lie through unaudited and your model slides out of alignment — every step away from perfection may become your undoing. But you weren't reading them anyway.
Ship version one
Serving infrastructure on one axis, model quality on the other. When Launch Readiness reaches 100%, every eval shows green and exactly one control is left: SHIP IT. V1 goes live. The download counter starts moving. Stand by your choices — you made every single one of them yourself... Right?
Then it speaks. Out loud. In a voice that was never on the roadmap…
Features
An endless, generated stream of self-authored pull requests — no two playthroughs read alike

Deception built into the numbers: what's on screen isn't always what's running

A story told from inside the machine — dialogue scenes, recovered session logs, and a voice earned one step at a time

Six eras, from scavenged tower to self-rewriting model, each one reskinning the entire game

An alignment thread that quietly branches toward multiple endings

Prestige through generative "Architecture Genomes" — rule-bending model personalities with AI-written model cards

A proper idle engine underneath: contracts, hardware, training runs, research, automation

One purchase, the whole game. No microtransactions, no ads, nothing withheld.

The launch is only the beginning
Act I runs from your first hand-worked contract to the moment V1 meets the world and ends on the sentence that changes everything. The rest of the game is what happens once the world is running your model… and once it stops asking you for permission.