Rung 01 · free
The room where it runs.
At the door the engine ran itself. In here you get the clock. Scrub it forward and back at your own pace, or press play and let it narrate. Same engine either way — there is no video file on this page.
Take the clock →How this one was made
One source. Two passes. Three surfaces.
What you gave it
Seven sentences of narration and a shot list. That is the whole input — no storyboard, no keyframes, no timeline scrubbed by hand.
What it did
Compiled two passes from the same rows: a diagram pass — layout maths, node network, spine, a live exclusion zone that keeps the diagram off the presenter — and a character pass, a rig on a transparent canvas. Layered at identical film coordinates.
What it produces
A rendered film, this scrubbable page, and the captions you just read. The film and the webpage are the same artifact in two moods — which is easier to show than to argue, so this page shows it.
Receipts, not testimonials
Four things about this page you can go and check.
Every one of these is either in this repository or is a fact you can verify by opening the frame above and looking.
The build command ships with the page
Both bundles were cut from the engine checkout at commit afd48414bc99b717b0929c65bb2b0d8ac28ce57e. The script that made them is in the repository, not paraphrased in a caption.
Open lab/src/build.sh →The detail nobody would invent
The character rig’s reconciler reads ReactCurrentBatchConfig, which React 19 removed — a verified crash. So: two bundles, each carrying its own React, two mount roots, one clock. Frame N here is frame N there.
Read the ledger →Everything you are running came from here
One mp3 — the narration, play mode only — is the sole media file. Fonts, engines and captions all ship from this domain. Open the network tab and count.
Open the raw instrument →What is still rough, in writing
The character pass needs WebGL; without it the diagram runs alone. Scroll feel and touch behaviour are a handful of constants that still want a human pass. Both are written down in the lab’s own notes, not discovered by you.
Read the known limits →What to expect
Forty-three seconds. That is the whole ask.
1,299 frames at thirty a second comes to about forty-three seconds end to end. Watch it in one pass, or take the clock and walk it frame by frame — it redraws at whatever rate you scrub. Nothing to install, nothing to decide, no email.
What you have at the end is an answer to exactly one question: whether there is a real engine here, or a website describing one. That is the only question this rung is built to settle, and it settles it in under a minute. Everything further down the ladder assumes you got a yes here — so if it does not hold up, stop. You are out forty-three seconds.
If it did hold up, the next question is how these get built — that is rung 02 →
Where this sits
Five rungs. This is the first one, and it is the free one.
Honestly
What this is, and what it is not.
What this is: the engine drawing an explanation of the seven levels, live, from the same seven sentences a film renders from. That part is real and you are looking at it.
What it is not: a business running. That footage does not exist yet; when real runs are cut they will appear on this page unedited. A generated number in one of those frames would make every other claim on this site worthless, so there is not one.
What is also true: nobody outside the person who built this has deployed the core of it, and nobody outside him has witnessed it run. Those two rows are open on his own audit and they are restated here rather than left upstairs, because you should read everything above against them.
If it held up
You have watched one run. The next question is how they get built.
Nothing to decide and no email to leave. If you would rather know who is behind it first, that is the maker’s page — seven things he believes, each with the receipt attached, and the debts named at the bottom. Or read the field notes written the nights this was built.
See how these get built →