| # | Beat | Timecode | Motion | Logo | Audio | VO / on-screen |
|---|---|---|---|---|---|---|
| 1 | open | 0–7.9s | spatial-parallax | icon·white-knockout | ♪ — | The server falls over at two in the morning. Who is awake to catch it, and how fast can they fix it? on-screen: The 2am server alert |
| 2 | legacy | 7.9–14.9s | crossfade-8f | icon·white-knockout | ♪ — | The old way: one admin who knows where everything is, and a wiki nobody updated since the last hire. on-screen: The one person who knows |
| 3 | teach | 14.9–21.9s | kinetic-build | icon·liquid-chrome | ♪ — | We describe the servers in a file, so the setup is readable, repeatable, and never a guess. on-screen: Step 1: infra as code |
| 4 | teach | 21.9–28.9s | kinetic-build | icon·white-knockout | ♪ — | Each service exposes a heartbeat the system pings constantly, so we know it is down before a user does. on-screen: Step 2: health checks |
| 5 | teach | 28.9–36.4s | kinetic-build | icon·liquid-chrome | ♪ — | When an alert fires, an agent pulls the recent logs and summarizes the likely cause before a human even reads it. on-screen: Step 3: agent triages logs |
| 6 | teach | 36.4–43.4s | kinetic-build | icon·white-knockout | ♪ — | We schedule backups and then actually restore one on a test box, because an untested backup is just hope. on-screen: Step 4: backups you tested |
| 7 | proof | 43.4–50.9s | receipts-count | icon·liquid-chrome | ♪ — | That is a stack that warns early, explains itself, and can be rebuilt from a file when it has to be. on-screen: Quiet pager, fast recovery |
| 8 | futurist | 50.9–56.9s | spatial-parallax | icon·white-knockout | ♪ — | When recovery is a command and not a crisis, you can experiment without fearing the 2am call. on-screen: What this unlocks |
| 9 | resolve | 56.9–62.9s | coalescence | stacked·white-knockout | ♪ swell | Want to know where your single points of failure are? We will map them. temerarii.xyz. on-screen: Audit your stack |