Back Office · office.temerarii.xyz
One published post, granular — the Social for W35 Fri, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW35-Fri-social-4kindSocialweekW35dayFridate2026-09-04campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

SaaS
copy ready · render pending

Output-policy spec format · dimensions (asset_specs.output_policy)

formatnative cut · 9:16 · 1:1 · 16:9 dims1080×1920 · 1080×1080 · 1920×1080 cadence5/day floor × 9 channels

Channels 9 destinations

TikTokInstagramLinkedInX/TwitterFacebookThreadsPinterestBlueskyYouTube

This post a distinct social asset — its own angle, storyboard, and cuts

social-W35-Fri-4
5-distinct-social/day · 9:16 master → 1:1 / 16:9 cuts per channel

Channel-cuts this asset → 9 native captions (one master · per-platform aspect+copy)

ChannelNative caption
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

Composition layer × scene 9 scenes · this post's OWN storyboard (distinct per asset)

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–5.9sspatial-parallaxicon·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
2s2
matches intent
shared field
signature-3d
hook5.9–12.9skinetic-buildicon·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
3s3
matches intent
NumberedList
template
teach12.9–19.5skinetic-buildicon·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
4s4
matches intent
RankList
template
proof19.5–25.8sreceipts-counticon·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
5s5
matches intent
BuildLog
template
diff25.8–33.1scrossfade-8ficon·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
6s6
matches intent
ChecklistCard
template
teach33.1–39.0skinetic-buildicon·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
7s7
matches intent
StatScoreboard
template
proof39.0–46.0sreceipts-counticon·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
8s8
matches intent
PipelineMap
template
step46.0–52.6skinetic-buildicon·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
9s9
matches intent
shared field
signature-3d
resolve52.6–59.2scoalescenceicon·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

Cross-links this post in the day's output set