Back Office · office.temerarii.xyz
One asset, all the way in — composition, the wireframe + storyboard, the output format stack, and the template, all read from the SAME content-index record. The expected output matches what /media surfaces for this post.
post longform-W24-Wedkind longformweek W24date 2026-06-17campaign longform-youtubepillar it_devbeat asset videoduration 186.7sground blackscenes 8

Checklist the per-video bar — engine/sim

100.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W24-Wed good|bad)
✓ all static checks pass — one-focal/scene · tier-by-beat · one-track caption · colorway · cast+shape correct · no banned/fabricated. (audio + visual tiers verify on the rendered finals — Phase 2)

Composition comp · template family · expected output

composition LongFormChaptersfamily / template LongFormChapters
9:16 Reelpending1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
render pending — silent master not yet on disk
expected output: 0/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 8 scenes · 186.7s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–25.9sspatial-parallaxicon·white-knockout♪ bed_in
One machine, eight pillars, all week. Today is motion graphics, the moving part of a brand. Most people animate by dragging keyframes in an app for hours. We do it differently: we write motion as code, so the same move plays the same way forever and a model can build it. By the end you will know how to make a logo move with a few lines instead of a timeline.
on-screen: Motion you can write down
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Motion you can write down
2s2
matches intent
NumberedList
template
teach25.9–50.0skinetic-buildicon·wireframe♪ node_lock
Step one. Use Remotion, a tool that lets you build video in React, which is just code that describes what is on screen. Instead of a timeline you write a component, and each frame is calculated. Why bother? Because code can be repeated, reviewed, and generated. Once your animation is a file, an agent can produce a hundred versions of it without you touching a mouse.
on-screen: Animate in code with Remotion
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Animate in code with Remotioncurate items, nodes
3s3
matches intent
ChecklistCard
template
teach50.0–73.8skinetic-buildicon·wireframe♪ node_lock
Step two. The core idea is simple: everything moves based on the current frame number. Frame zero, the logo is small. Frame thirty, it is full size. You map frame to position with a function called interpolate, which just draws a straight line between two values. That is motion in one sentence: pick a start, pick an end, let the frame number slide between them.
on-screen: Drive movement from the frame number
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Drive movement from the frame numbercurate items, nodes
4s4
matches intent
StepFlow
template
teach73.8–96.1skinetic-buildicon·wireframe♪ node_lock
Step three. Straight-line motion looks robotic, so swap interpolate for spring. Spring is a built-in function that makes things settle like real objects, a tiny overshoot and a soft stop. You give it the frame and it returns a natural value. One word change turns a stiff slide into a move that feels alive, and you never hand-tuned a single curve.
on-screen: Make it feel alive with spring
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Make it feel alive with springcurate nodes, steps
5s5
matches intent
JsonDiff
template
teach96.1–119.1skinetic-buildicon·wireframe♪ node_lock
Step four. Build your animation so the text and colors come in as inputs, not baked in. In Remotion these are called props. Now the same motion template can render Monday's headline and Tuesday's, just by passing different words. You designed the move once. The machine fills it with new content every day, and the brand motion stays identical across all of it.
on-screen: Reuse one scene, change the words
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Reuse one scene, change the wordscurate fileName, lines, nodes
6s6
matches intent
StackTrace
template
teach119.1–142.1skinetic-buildicon·wireframe♪ node_lock
Step five. The payoff is rendering. From your terminal you run one command and Remotion turns the code into a finished video file. Point an agent at a list of headlines and it loops the command, producing a full week of motion graphics while you do something else. You stopped exporting clips one by one and started shipping a batch from one line.
on-screen: Render the whole batch from the terminal
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Render the whole batch from the terminalcurate errMsg, errType, fix, frames, nodes
7s7
matches intent
RankList
template
proof142.1–163.7sreceipts-counticon·wireframe♪ node_lock
The proof is everything moving on our calendar. The shapes, the logo reveals, the captions sliding in, all of it is Remotion code driven by frame numbers, rendered from the terminal. We did not animate hundreds of videos by hand. We wrote the moves once and let the machine render the rest, on the same three colors, every day.
on-screen: Our whole calendar renders this way
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Our whole calendar renders this waycurate rows, statsLabels
8s8
matches intent
shared field
signature-3d
resolve163.7–186.7scoalescenceicon·white-knockout♪ bed_out
So motion graphics is not a timeline you babysit, it is code you write and a machine renders. Drive it by frame, soften it with spring, feed it props, render the batch. Your next step: install Remotion and animate one box moving across the screen. That is the whole idea in miniature. Watch ours run, in public, at office dot temerarii dot xyz.
on-screen: See the motion run live
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→See the motion run live

Format stack 1 aspects · same scenes[], re-cropped

16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 2 destinations

YouTubeBlog

Social captions supplemental published copy · per channel (comp_id level)

youtubeAnimate Video You Can Write Down, Then Render the Whole Batch This video shows motion you can write down, so a single scene becomes hundreds of videos from the terminal instead of one hand-animated clip at a time. What you will learn: - Animate in code with Remotion: build the video as React components, so the motion is text you can read, version, and reuse. - Drive movement from the frame number: every position and fade is a function of the current frame, so the same code renders the same way every time. - Make it feel alive with spring: a spring gives motion a natural ease-in and settle instead of a flat, robotic slide. - Reuse one scene, change the words: feed the same composition different content and it draws a new video, on brand, without a redesign. - Render the whole batch from the terminal: one command loops your content and outputs every asset. Then the proof: our whole calendar renders this way, one composition fed by data, producing every video in every aspect ratio. Keywords: Remotion, programmatic video, React animation, spring, batch rendering, motion design. See the whole system run in public at temerarii.xyz.

Cross-links every lens is a view on this one record