engine.sim.memory review longform-W26-Wed good|bad)| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 | ![]() matches intent shared field signature-3d | open | 0–21.3s | spatial-parallax | icon·ember-fill | ♪ bed_in | If it works on us, it works for you. Today, motion graphics. Animation is where brands usually fall apart, because someone opens a new app and forgets the rules. We do it differently. We build motion with code, so it cannot drift off brand. Today I will show you how we make things move without losing the thread. on-screen: Motion that obeys the brand |
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Motion that obeys the brand | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 21.3–44.7s | kinetic-build | icon·color | ♪ node_lock | First move: we use Remotion, a tool that lets you build video frame by frame in React, the same language as a website. So our video reads the exact same token file as everything else. The red is the brand red because it is literally the same value. You are not eyeballing a color in a timeline. You are pulling it from one source. on-screen: Build video in React |
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape boxground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Build video in Reactcurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 44.7–66.30000000000001s | kinetic-build | icon·color | ♪ node_lock | Second move: we write our motion rules down too. How fast things ease in, how long a beat holds, the floor on a scene length. Those live in the brand rails, in plain text. The agent reads them and animates inside the lines. So every clip feels like the same hand made it, because the same rules made it. on-screen: Make motion a rule, not a feeling |
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Make motion a rule, not a feelingcurate items, nodes | |||||||
| 4 | ![]() matches intent SchematicCard template | teach | 66.3–87.6s | kinetic-build | icon·color | ♪ node_lock | Third move: the coding agent writes the Remotion composition for you. You describe the beats, it lays out the scenes, picks the tokens, and times the moves to the rules. Then you press render in the terminal. No dragging clips for an hour. You review the output, fix the prompt, render again. The loop is minutes, not days. on-screen: Let the agent write the timeline |
expected on screen: white ground · a SchematicCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id SchematicCardvisual node-graphshape boxground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Let the agent write the timelinecurate nodes | |||||||
| 5 | ![]() matches intent PipelineMap template | teach | 87.6–106.0s | kinetic-build | icon·color | ♪ node_lock | Fourth move: because it is code, one composition can output many shapes. Tall for a phone, wide for a screen, all from the same file. We render the vertical and the widescreen from one source, so they always match. Change the brand once, re-render, and every aspect ratio updates together. on-screen: One render becomes nine cuts |
expected on screen: white ground · a PipelineMap panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id PipelineMapvisual node-graphshape boxground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→One render becomes nine cutscurate nodes, stages | |||||||
| 6 | ![]() matches intent ComparisonTable template | proof | 106.0–122.3s | receipts-count | icon·color | ♪ node_lock | The proof is on screen. The motion you are watching right now came out of this exact pipeline: tokens, rules, agent, render. We did not hand-animate it in a separate tool. It is the same machine we are describing, running on itself, in public. on-screen: Our own clips prove it |
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Our own clips prove itcurate colA, colB, rows, statsLabels | |||||||
| 7 | ![]() matches intent shared field signature-3d | resolve | 122.3–142.8s | coalescence | icon·ember-fill | ♪ bed_out | Your next step: stop animating in a vacuum. Put your motion rules in text, build clips in Remotion off your tokens, and let an agent write the timeline. See our motion living across the calendar at office dot temerarii dot xyz. Motion that follows rules is motion that still looks like you a hundred clips later. on-screen: Move things with rules |
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Move things with rules | |||||||