| # | Beat | Timecode | Motion | Logo | Audio | VO / on-screen |
|---|---|---|---|---|---|---|
| 1 | open | 0–7.9s | spatial-parallax | icon·liquid-chrome | ♪ — | An event recap used to land a week late, after everyone moved on. We can have it posted before the room empties. on-screen: Recap reel before guests leave |
| 2 | legacy | 7.9–14.9s | crossfade-8f | icon·wireframe | ♪ — | The old way: shoot all day, dump cards that night, then edit for a week while the moment cooled off. on-screen: Old way: edit for a week |
| 3 | teach | 14.9–23.5s | kinetic-build | icon·wireframe | ♪ — | It starts on the floor: capture with a shot list, not at random, so the footage is already sorted by the story you'll tell. on-screen: Step 1: capture with intent |
| 4 | teach | 23.5–30.5s | kinetic-build | icon·wireframe | ♪ — | Each clip gets tagged on ingest by moment, keynote, crowd, hallway, so the edit map is built before editing starts. on-screen: Clips tagged as they land |
| 5 | teach | 30.5–37.5s | kinetic-build | icon·wireframe | ♪ — | We run the keynote audio through Whisper, then pull the one quotable line as the spine of the recap. on-screen: Transcribe -> pull the line |
| 6 | teach | 37.5–44.5s | kinetic-build | icon·wireframe | ♪ — | Then it flows: tagged clips plus the chosen quote feed an FFmpeg assembly that stitches the vertical recap automatically. on-screen: Tags -> FFmpeg -> cut reel |
| 7 | proof | 44.5–50.5s | receipts-count | icon·wireframe | ♪ — | The recap goes live the same day, while attendees are still posting their own photos. on-screen: Posted same day |
| 8 | futurist | 50.5–56.5s | spatial-parallax | icon·wireframe | ♪ — | Soon every event ships its own story the moment it ends, and next year's promo writes itself. on-screen: Every event, instant story |
| 9 | resolve | 56.5–62.5s | coalescence | stacked·liquid-chrome | ♪ swell | Got an event coming up? We'll capture it and post the recap before the lights come up. temerarii.xyz. on-screen: Cover your next event |