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-W25-Wedkind longformweek W25date 2026-06-24campaign longform-youtubepillar strategic_relationsbeat asset videoduration 147.4sground redscenes 6

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-W25-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 6 scenes · 147.4s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–23.4sspatial-parallaxicon·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
2s2
matches intent
NumberedList
template
teach23.4–48.2skinetic-buildicon·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
3s3
matches intent
ChecklistCard
template
teach48.2–73.0skinetic-buildicon·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
4s4
matches intent
NodeGraphCard
template
teach73.0–97.8skinetic-buildicon·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
5s5
matches intent
KpiGrid
template
proof97.8–122.6sreceipts-counticon·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
6s6
matches intent
shared field
signature-3d
resolve122.6–147.4scoalescenceicon·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

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)

youtubeMotion That Means Something: Tie Every Move to a Meaning Animation for its own sake is noise. This video shows how to make motion that means something, where every move on screen carries a point. What you will learn: - Animate with code, not by hand: build the motion in code so it is repeatable and tied to the content, not nudged frame by frame. - Tie each move to a meaning: a thing rises because it matters, a thing locks because it is decided. The motion explains, it does not just decorate. - Caption and motion are one track: the words and the movement say the same thing at the same time, so the viewer never has to choose where to look. Then the proof: our motion is one system, not many. Code it once and render it everywhere, so every clip moves in the same language and the movement always carries weight. Keywords: motion design, meaningful animation, Remotion, code animation, caption sync, video. See the whole system run in public at temerarii.xyz.

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