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 social-W24-Thu-4kind threadweek W24date 2026-06-18campaign thread · Thupillar brandbeat Thuasset videoduration 56.9sground redscenes 9

Checklist the per-video bar — engine/sim

95.7/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W24-Thu-4 good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_generictoo_complex · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel
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 · 56.9s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–5.2sspatial-parallaxicon·liquid-chrome♪ bed_in
Most teams make one animation and then jam it into nine wrong sizes.
on-screen: One animation, nine wrong sizes
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape icosaground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→One animation, nine wrong sizes
2s2
matches intent
shared field
signature-3d
hook5.2–11.8skinetic-buildicon·white-knockout♪ node_lock
Here is how The Big T-M scales motion to every feed without redoing the work nine times.
on-screen: How AI scales motion correctly
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape icosaground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→How AI scales motion correctly
3s3
matches intent
NumberedList
template
teach11.8–18.8skinetic-buildicon·liquid-chrome♪ node_lock
Build the animation as code with the text and timing as inputs, not baked into a video file.
on-screen: Build it as code, not a video
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape icosaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Build it as code, not a videocurate items, nodes
4s4
matches intent
RankList
template
proof18.8–25.8sreceipts-counticon·white-knockout♪ node_lock
The proof: change the size or the words and you re-render in minutes instead of re-animating for days.
on-screen: Re-render, never re-animate
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape icosaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Re-render, never re-animatecurate rows, statsLabels
5s5
matches intent
DiffCard
template
diff25.8–32.4scrossfade-8ficon·liquid-chrome♪ node_lock
The old way was exporting each format by hand and praying the captions stayed inside the frame.
on-screen: Old way: export each one by hand
expected on screen: red ground · a DiffCard panel over a dimmed Signal Field · Signum leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual codeshape icosaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Old way: export each one by handcurate codeLines, lines
6s6
matches intent
ChecklistCard
template
teach32.4–39.4skinetic-buildicon·white-knockout♪ node_lock
Now you let a model rough out the in-between frames, then you fix the timing so it breathes.
on-screen: Let AI draft the in-betweens
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape icosaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Let AI draft the in-betweenscurate items, nodes
7s7
matches intent
StatScoreboard
template
proof39.4–46.4sreceipts-counticon·liquid-chrome♪ node_lock
The receipt is energy that survives the crop: vertical, square, and wide all feel like the same piece.
on-screen: Same energy, every aspect ratio
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape icosaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Same energy, every aspect ratiocurate pillar, stats, statsLabels
8s8
matches intent
ListCard
template
step46.4–51.9skinetic-buildicon·white-knockout♪ node_lock
Set safe zones for captions once, so nothing important ever hides behind the interface.
on-screen: Caption-safe zones, always
expected on screen: red ground · a ListCard panel over a dimmed Signal Field · Signum leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual pipelineshape icosaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Caption-safe zones, alwayscurate items, stages, steps
9s9
matches intent
shared field
signature-3d
resolve51.9–56.9scoalescenceicon·liquid-chrome♪ bed_out
Make it once and ship it everywhere, properly.
on-screen: Make it once, ship it everywhere
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Make it once, ship it everywhere

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)

tiktokMost teams make one animation and jam it into 9 wrong sizes. AI-assisted: build motion as CODE with text and timing as inputs, then re-render every size in minutes. Let AI rough the in-betweens, you fix the timing. Method below.
instagramOne animation, nine wrong sizes? No. Build motion as code. Text + timing as inputs. Re-render, don't re-animate. Caption-safe zones always. #motiongraphics #animation #design #motiondesign #temerarii
linkedinMost teams make one animation and then jam it into nine wrong sizes. How we scale motion correctly: build the animation as code with text and timing as inputs instead of baking it into a video file, so changing the size or words re-renders in minutes rather than re-animating for days. Let a model rough out the in-between frames, then fix the timing so it breathes, and set caption-safe zones once. Takeaway: make it once and ship it everywhere, properly.
xOne animation jammed into 9 wrong sizes? No. Build motion as code → text + timing as inputs → re-render, don't re-animate. Make it once, ship it everywhere. temerarii.com
facebookMost teams make one animation and then jam it into nine wrong sizes. Here's the move: build the animation as code with text and timing as inputs, not baked into a video file, so changing the size or the words re-renders in minutes. Let a model rough out the in-betweens, fix the timing, and set caption-safe zones once. Make it once and ship it everywhere. Want the method? It's on the site.
threadsOne animation jammed into nine wrong sizes? No. Build motion as code with text and timing as inputs, re-render every size in minutes, set caption-safe zones once. Make it once, ship it everywhere.
pinterestScalable motion graphics: how to build animation as code, use text and timing as inputs, re-render every aspect ratio, and set caption-safe zones. Plain-language motion design workflow guide for teams.
blueskyOne animation jammed into 9 wrong sizes? No. Build motion as code with text and timing as inputs, re-render every size in minutes. Make it once, ship it everywhere. temerarii.com
youtubeScale One Animation To Nine Feeds (Without Redoing It Nine Times) Most teams make one animation and then jam it into nine wrong sizes. This walkthrough shows how we scale motion correctly: build the animation as code with text and timing as inputs instead of baking it into a video, so changing size or words re-renders in minutes; let a model rough out the in-between frames, fix the timing so it breathes, and set caption-safe zones once. AI-assisted production. Give-it-away method from The Big T-M. Chapters: nine wrong sizes · build it as code · re-render not re-animate · AI in-betweens · caption-safe zones.

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