engine.sim.memory review longform-W25-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–23.4s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | Today is motion graphics, and we built ours in code, on ourselves, so you can see how it works. Most motion is decoration. Ours carries meaning. By the end you will know how we animate with Remotion, how we keep every video on brand without redrawing it, and why our motion explains the idea instead of just decorating it. Real steps, the real tool. on-screen: Motion that means something |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Motion that means something | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 23.4–48.2s | kinetic-build | icon·white-knockout | ♪ node_lock | We do not keyframe by hand for a hundred videos. We use Remotion, which lets you build animation as React code. A shape moving across the screen is a function of time, written once. Change one number and every video updates. The brain running it is Claude Code, calling Remotion to render. Motion as code means it scales, stays consistent, and never drifts the way hand work does. on-screen: Animate with code, not by hand |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Animate with code, not by handcurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 48.2–73.0s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Every motion in our system stands for something. A laser is navigation. Shapes coalescing is the idea coming together. We do not add a move because it looks busy. We add it because it says what the words say, at the same time. So before we animate, we name the meaning, then pick the move that carries it. Motion without meaning is just noise that costs render time. on-screen: Tie each move to a meaning |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Tie each move to a meaningcurate items, nodes | |||||||
| 4 | ![]() matches intent NodeGraphCard template | teach | 73.0–97.8s | kinetic-build | icon·white-knockout | ♪ node_lock | The bottom caption and the animation are not two jobs, they are one. The caption is a tight seven word version of what the voice says, and the motion lands on the same beat. We sync them in the same composition so they hit together. When the line says the idea comes together, the shapes come together. One point, said three ways at once, words, caption, and motion. on-screen: Caption and motion are one track |
expected on screen: red ground · a NodeGraphCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Caption and motion are one trackcurate hub, nodes | |||||||
| 5 | ![]() matches intent KpiGrid template | proof | 97.8–122.6s | receipts-count | icon·liquid-chrome | ♪ node_lock | The honest proof is consistency. Every video this week uses the same motion language, the same shapes, the same timing rules, because they all render from the same code. We did not animate them one by one and hope they matched. They match because they share a system. You can watch several side by side and see one hand behind all of them, which is the whole goal. on-screen: Our motion is one system, not many |
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Our motion is one system, not manycurate kpis, statsLabels | |||||||
| 6 | ![]() matches intent shared field signature-3d | resolve | 122.6–147.4s | coalescence | icon·liquid-chrome | ♪ bed_out | So motion graphics, our way. Animate in code with Remotion, not by hand. Tie every move to a meaning before you make it. Lock caption and motion to the same beat. Share one system so a hundred videos feel like one. That is motion that scales and still means something. See it moving live at office dot temerarii dot xyz, then go animate one idea, not one decoration. on-screen: Code it once, render it everywhere |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Code it once, render it everywhere | |||||||