| # | Beat | Timecode | Motion | Logo | Audio | VO / on-screen |
|---|---|---|---|---|---|---|
| 1 | open | 0–7s | spatial-parallax | icon·liquid-chrome | ♪ — | Everyone has the app idea. The gap is turning it into something that actually runs. on-screen: Your idea. Working software. |
| 2 | legacy | 7.0–14.0s | crossfade-8f | icon·white-knockout | ♪ — | The old way: a six-month spec, a contractor in another timezone, and a demo that broke on day one. on-screen: How it used to go |
| 3 | teach | 14.0–21.0s | kinetic-build | icon·liquid-chrome | ♪ — | We start by writing the whole feature as a plain-English spec, the same brief a junior dev would get. on-screen: Step 1: spec in plain English |
| 4 | teach | 21.0–28.0s | kinetic-build | icon·white-knockout | ♪ — | Then Claude Code reads the actual repository, so it edits your real files instead of inventing new ones. on-screen: Step 2: Claude Code reads the repo |
| 5 | teach | 28.0–35.0s | kinetic-build | icon·liquid-chrome | ♪ — | We have it write the failing test before the feature, so the definition of done is provable, not a feeling. on-screen: Step 3: tests first |
| 6 | teach | 35.0–42.5s | kinetic-build | icon·white-knockout | ♪ — | Every change lands as one small commit on a branch, so a bad idea is one revert away, never a rewrite. on-screen: Step 4: small commits |
| 7 | teach | 42.5–48.5s | kinetic-build | icon·liquid-chrome | ♪ — | We lock the data shapes with types, so the editor catches the bug before the user ever does. on-screen: Step 5: typed contracts |
| 8 | teach | 48.5–56.4s | kinetic-build | icon·white-knockout | ♪ — | Then we actually launch the app and click through it, because a passing test is not the same as it feeling right. on-screen: Step 6: run it, watch it |
| 9 | teach | 56.4–63.5s | kinetic-build | icon·liquid-chrome | ♪ — | A second pass reviews the diff against the main branch for the bugs the first pass talked itself out on-screen: Step 7: review the diff |
| 10 | teach | 63.5–70.6s | kinetic-build | icon·white-knockout | ♪ — | It goes out as a pull request with the tests green, so the merge is a decision, not a on-screen: Step 8: ship on a PR |
| 11 | teach | 70.6–76.6s | kinetic-build | icon·liquid-chrome | ♪ — | After deploy we open the live URL and confirm the thing we built is the thing that loaded. on-screen: Step 9: verify in prod |
| 12 | proof | 76.6–83.39999999999999s | receipts-count | icon·white-knockout | ♪ — | That loop, spec to test to commit to ship, is how a feature goes from sentence to live software. on-screen: Spec to running app |
| 13 | futurist | 83.4–89.4s | spatial-parallax | icon·liquid-chrome | ♪ — | When the loop is this tight, the bottleneck stops being engineering and becomes deciding what to build. on-screen: What this unlocks |
| 14 | resolve | 89.4–95.4s | coalescence | stacked·liquid-chrome | ♪ swell | Bring the idea. We will show you the spec-to-ship loop running on it. Start at temerarii.xyz. on-screen: Bring the idea |