The map
How the engine works: one loop, run per domain.
A world is a domain run like a company. The engine stands one up, runs the loop below inside it, and everything each turn produces becomes the input to the next.
Watch a world run →What the engine is made of
Five layers. Every world runs on the same five.
Point it at a different domain and the departments change. The stack underneath does not — which is the whole reason one engine can carry a plumbing company, a coding team and a body.
The open agent runtime everything else is built on
Free, installable, and inspectable on GitHub. Given away on purpose — the map is not the moat.
Agents act from a knowledge graph, not a flat prompt
What a world learns accumulates in a graph instead of resetting each session. This is the mechanism behind the word “compounds.”
Departments compile themselves from a written spec
You describe a department; the engine writes it and hires it. That is how a world grows its own team instead of you assembling one.
It checks the work against your rules before it acts
Written rules, checked at every hand-off — not a vibe check by the same model that produced the work. The reason the output holds up.
The world runs in rounds and grades its own last one
Each round reviews what the previous round claimed was finished, keeps what worked, and adjusts the next batch. A simulation, not a script.
The worlds that exist today
Two worlds and one world’s output. Nothing is listed here that you cannot open.
Jobworld — business
A CEO agent and five self-grading departments running a real outreach business: sourcing, writing, delivery, replies, measurement.
Have one run yours →HealthWorld — the body
Fourteen body systems as fourteen departments. The same pattern applied to a domain with no AI anywhere in it.
See the world →One world’s output
A complete local-business site — copy, layout, imagery — produced by a single run. The artifact, not a screenshot of it.
Open the build →Where this leads
From free to all-in, with a price on every rung.
Receipts, not testimonials
Don’t take my word for it — take the code.
No logo wall, no invented case studies. The engine is open source, the demo is a real site, the notes are out in the open, and even the safety position is published research: alignment at the joints, not in the weights — every hand-off checked, no component trusted on its word.
The engine, on GitHub
Installable and public: heaven-framework, chaincompiler, carton-mcp, skilltree. Read it, run it, fork it.
github.com/sancovp →A world running in your browser
The explainer renders as you scroll — the engine drawing its own explanation, on this domain.
Watch it run →What one run produced
A live local-business site produced by the system. Not a mockup, not a template screenshot.
See the build →A film, proved like a theorem
A full story structure — How to Train Your Dragon — run through the system end to end. Real output, published.
See the proof →What to expect
Not a better answer today. A system that still knows it next month.
The usual pitch in this category will not survive contact, so here is the version that does: on any single task, a well-written prompt matches this. One question at a time, side by side, you would not reliably pick the engine out of a line-up. Anyone claiming otherwise is selling you the demo.
What changes is the second step, and the tenth. A one-off answer is excellent and then it is gone. What is described above remembers, recalls what it already decided, commits to a structure up front instead of re-deciding it every turn, and extends itself when a job runs past what it knows. That difference does not show in a snapshot and is decisive over a month — which is an awkward thing to sell, and the honest thing to say.
So: nothing here is instant. Expect fast, coherent and self-operating, and expect the compounding to show over weeks rather than in the first sitting. Expect a person in the loop too — a human reviews the batch before it goes out, on purpose, every time.
The fastest way to test any of that is to open one and look — watch a world run →
Straight terms
What you’re buying, honestly.
Every rung above ships and runs today. You can install the engine this afternoon, and the worlds on this page are open, not screenshots.
What is not done: the worlds do not auto-wire into one another yet — you turn on the one you need, and joining two is still hand work. The embodied 3D version, where you walk into your own business, is a frontier, not a product. And nothing here is autonomous in the sense of unsupervised: a human reviews the batch before it goes out, on purpose, every time.
So: you are buying the system that exists, plus the roadmap it is on, from the person building it. No income promises. No “fully autonomous.” A real company, and the real machine under it. Every rung’s terms sit on one page — read them against this band, not instead of it.
Start at the bottom
You’ve seen the loop. Now watch one turn of it.
No email, nothing to decide. The fastest way to find out whether any of this survives contact is to open the thing and look.
Watch a world run →