Simulations and world loops
You’re inside one right now.
I build worlds that do work — a business, a body, a codebase, each with departments, an economy and a record of what it actually did. One engine. Many worlds. A loop that compounds. The thing moving to the left is that engine, drawing its own explanation, live.
Enter →Free. No email. About four minutes. You can leave whenever — and the way out is the same door. · Who built this · How it works
Three ways down
Pick the thread you’d actually pull.
These go to different places on purpose. One ends in source code, one ends in a business running, one ends in a world you can walk around in. All three are free and none of them ask you for anything.
I want to see the code that does this.
The runtime, the compiler, the team library. Public, installable, old enough to have a history you can read. It ends in a clone command, not a contact form.
Open the source →I want one of these running my business.
A CEO agent and five departments that source, write, deliver, read the replies and grade their own last round. What it does, what it refuses to do without a human, and what it can’t do yet — all on one page.
See the business world →I just want to look around.
The room where the engine runs, and the field notes written the night the work happened — the diagrams playing live, the receipts one click down.
Walk through it →Where to start
Five rungs. Climb as far as you want, stop wherever you like.
The category claim
Same engine. Different world.
A world is a domain run like a company: departments, signals, maintenance schedules, routing, failure cascades. Change the domain and the departments change. The engine underneath does not.
Jobworld — business
A CEO agent and self-grading departments doing the outreach, the writing, the delivery and the measurement. Your company, running itself, with you reviewing the work.
Have one run your business →HealthWorld — the body
Fourteen body systems as fourteen departments — each with visibility, a maintenance cadence, and a professional to route to. Same pattern, no AI anywhere in the domain.
See the world →Why it compounds
The loop, in one line.
You’re reading the output of this loop right now. The marketing isn’t separate from the product — the product produces the marketing. This site, its notes, and the explainer above were built by the thing being sold. The proof isn’t a testimonial. The proof is that it exists.
Receipts, not testimonials
Don’t take my word for it — take the code.
No logo wall, no invented case studies. The proof is public: the engine is open source, the demo is a real site, and the notes are out in the open.
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
Not a video of a demo. The thing itself, rendering as you scroll, on this domain.
Watch it run →What one run produced
A live local-business site — copy, layout, imagery, the lot — produced by the system. Not a mockup.
See the build →Fifty-plus field notes
The research behind the work, published as it was written — not cleaned up afterwards, not locked in a deck.
Read the notes →Start at the bottom
Nothing to decide. You already saw it run.
It costs nothing and asks for no email. If it doesn’t hold up, you’ve lost a few minutes and learned something true about the claim. If you’d rather know who’s behind it: the maker.