engine.sim.memory review longform-W40-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–27.0s | spatial-parallax | icon·white-knockout | ♪ bed_in | Who you are is not only how you look standing still. It is how you move. Today is motion graphics, and the trap is treating motion as decoration sprinkled on at the end. Motion is meaning. The way your logo enters tells people if you are calm or frantic. By the end you will know how to build brand motion in code, so it is consistent, repeatable, and never redrawn by hand at midnight. on-screen: Make the brand move |
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape icosaground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Make the brand move | |||||||
| 2 | ![]() matches intent NumberedList template | teach | 27.0–52.5s | kinetic-build | icon·white-knockout | ♪ node_lock | Step one. Use Remotion. It lets you build video in React, which means your animation is code, not a timeline you drag. The win is that code repeats perfectly. Define your logo entrance once as a function, and every video this year uses the exact same motion. We render our whole calendar this way. No human re-keyframing the same move two hundred times and getting it slightly wrong each time. on-screen: Animate in code, not by hand |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape icosaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Animate in code, not by handcurate items, nodes | |||||||
| 3 | ![]() matches intent ChecklistCard template | teach | 52.5–80.9s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Step two. Pick your motion rules and write them as numbers in one config file. How long an entrance takes. How fast things ease. Whether motion is sharp or soft. Those numbers are brand decisions, same as a color. Save them once and have every composition import them. Change the file, and the next render moves the new way everywhere. Your motion becomes a system you tune in one place, not a habit you re-explain to every editor. on-screen: Set timing as brand rules |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape icosaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Set timing as brand rulescurate items, nodes | |||||||
| 4 | ![]() matches intent WireframeMock template | teach | 80.9–108.60000000000001s | kinetic-build | icon·white-knockout | ♪ node_lock | Step three. Real things speed up and slow down, they do not move at one flat rate. Use an easing curve, a spring, so motion feels alive instead of mechanical. In Remotion you can drive it with a spring function and tune stiffness and damping until it feels like your brand. Too bouncy reads as goofy, too stiff reads as cold. Pick one feel, put the numbers in your config, and never argue about it again. on-screen: Ease like a body, not a robot |
expected on screen: red ground · a WireframeMock panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id WireframeMockvisual node-graphshape icosaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Ease like a body, not a robotcurate nodes | |||||||
| 5 | ![]() matches intent BuildLog template | proof | 108.6–131.6s | receipts-count | icon·liquid-chrome | ♪ node_lock | Proof, no numbers. Every motion you see this week was rendered from code, from the same timing config, with the same spring. The logo enters identically because a function says so, not because someone remembered. We can change the studio's whole motion feel by editing one file and re-rendering. You are watching the result of that system right now, built in the open. on-screen: We render every video in code |
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual receiptsshape icosaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We render every video in codecurate lines, statsLabels | |||||||
| 6 | ![]() matches intent shared field signature-3d | resolve | 131.6–159.29999999999998s | coalescence | icon·white-knockout | ♪ bed_out | So motion graphics done right is code, not dragging. Animate in Remotion, store your timing as numbers in one file, ease with a spring so it feels alive, and let every video import the same rules. Do that and your brand moves the same way forever, on purpose. The whole motion system runs in public at office dot temerarii dot xyz. Open one composition, change one number, and watch the brand move differently everywhere at once. on-screen: Build it at office.temerarii.xyz |
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Build it at office.temerarii.xyz | |||||||