Checklist the per-video bar — engine/sim
84.5/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W35-Fri-4 good|bad)⚠ 4 flag(s) — not yet ship-ready: copy_generictoo_complexdup_sequence_across_assetsdup_set_across_assets · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
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 9 scenes · 59.2s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  matches intent shared field signature-3d | open | 0–5.9s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | Teams used to rebuild the same intro animation from scratch for every single new video. on-screen: Animators redoing the same intro |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Animators redoing the same intro | |||||||
| 2 |  matches intent shared field signature-3d | hook | 5.9–12.9s | kinetic-build | icon·white-knockout | ♪ node_lock | Now we template the motion once, then swap the content, so the look stays and the work shrinks. on-screen: Template the motion, swap the content |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Template the motion, swap the content | |||||||
| 3 |  matches intent NumberedList template | teach | 12.9–19.5s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Build the animation in code, so a text file of words and colors drives the whole render. on-screen: Build it in code, not by hand |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Build it in code, not by handcurate items, nodes | |||||||
| 4 |  matches intent RankList template | proof | 19.5–25.8s | receipts-count | icon·white-knockout | ♪ node_lock | Feed it a row from a spreadsheet, and out comes one finished video, perfectly on brand. on-screen: Feed it a row, get a video |
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape dodecaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Feed it a row, get a videocurate rows, statsLabels | |||||||
| 5 |  matches intent BuildLog template | diff | 25.8–33.1s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | This is not one render you babysit, it is a small factory that runs the same recipe every time. on-screen: Not one render, a factory |
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape dodecaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Not one render, a factorycurate codeLines, lines | |||||||
| 6 |  matches intent ChecklistCard template | teach | 33.1–39.0s | kinetic-build | icon·white-knockout | ♪ node_lock | Change a rule in the template once, and every future video inherits the fix automatically. on-screen: Change the rule, fix every video |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Change the rule, fix every videocurate items, nodes | |||||||
| 7 |  matches intent StatScoreboard template | proof | 39.0–46.0s | receipts-count | icon·liquid-chrome | ♪ node_lock | A hundred clips can ship in a day, each different in words but identical in style and pace. on-screen: A hundred cuts, one style |
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→A hundred cuts, one stylecurate pillar, stats, statsLabels | |||||||
| 8 |  matches intent PipelineMap template | step | 46.0–52.6s | kinetic-build | icon·white-knockout | ♪ node_lock | Step one is coding one solid template, before you try to make a single batch of videos. on-screen: Code one template first |
expected on screen: red ground · a PipelineMap panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id PipelineMapvisual pipelineshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Code one template firstcurate stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 52.6–59.2s | coalescence | icon·liquid-chrome | ♪ bed_out | Make the motion once, render it forever. That is how The Big T-M does motion at scale. on-screen: Make once, render forever |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Make once, render forever | |||||||
Format stack 3 aspects · same scenes[], re-cropped
9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video
Channels 9 destinations
LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky
Social captions supplemental published copy · per channel (comp_id level)
tiktokStop rebuilding the same intro for every video. Build the animation in code so a text file of words and colors drives the render, then feed it a spreadsheet row and out comes a finished, on-brand video. A hundred cuts, one style, in a day. (AI-assisted edit.)
instagramTemplate the motion, swap the content.
Build it in code, not by hand.
Feed it a row, get a video.
It's a factory, not one render.
Change the rule, fix every video.
#motiongraphics #animation #automation #design #temerarii
linkedinTakeaway on motion at scale: template the motion once, then swap the content.
Teams used to rebuild the same intro from scratch for every video. Instead, build the animation in code so a text file of words and colors drives the entire render. Feed it a row from a spreadsheet and out comes one finished, on-brand video. This isn't a single render you babysit; it's a small factory running the same recipe every time. Change a rule in the template once and every future video inherits the fix. A hundred clips can ship in a day, different in words but identical in style and pace. Code one solid template first.
xMotion-at-scale truth: stop rebuilding the same intro every time. Build it in code so a text file drives the render, feed it a spreadsheet row, get a finished on-brand video. Change the rule once, fix every video. temerarii.com
facebookTeams used to rebuild the same intro animation from scratch for every video. The fix: template the motion once, then swap the content. Build the animation in code so a text file of words and colors drives the render, feed it a spreadsheet row, and out comes a finished, on-brand video. Change a rule once and every future video inherits the fix. A hundred cuts, one style, in a day. More at temerarii.com.
threadsStop rebuilding the same intro for every video. Build the animation in code so a text file of words and colors drives the render, then feed it a spreadsheet row and out comes a finished, on-brand video. Change the rule once, fix every video. A hundred cuts in a day.
pinterestMotion graphics at scale guide: build animations in code, drive renders from a data file, feed spreadsheet rows to generate finished on-brand videos, and update one template rule to fix every video. Evergreen automated video production and motion design strategy.
blueskyMotion-at-scale truth: stop rebuilding the same intro every time. Build it in code so a text file drives the render, feed it a spreadsheet row, get a finished on-brand video. Change the rule once, fix every video. temerarii.com
youtubeMotion Graphics at Scale: Template Once, Render Forever
Teams used to rebuild the same intro animation from scratch for every single video. The fix: template the motion once, then swap the content. Build the animation in code so a text file of words and colors drives the whole render. Feed it a row from a spreadsheet and out comes one finished, on-brand video. This is a small factory, not a render you babysit. Change a rule in the template once and every future video inherits the fix. A hundred cuts can ship in a day, identical in style and pace.
More at temerarii.com.
#motiongraphics #animation #automation