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-W23-Thu-4kind threadweek W23date 2026-06-11campaign thread · Thupillar performancebeat Thuasset videoduration 48.6sground blackscenes 9

Checklist the per-video bar — engine/sim

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

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel
9:16 Reelrendered1:1 Squarerendered16:9 Widerendered9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 3/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 9 scenes · 48.6s · 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.0sspatial-parallaxicon·white-knockout♪ bed_in
Email newsletters used to be a monologue shouted at a silent crowd.
on-screen: Newsletters were a monologue
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Newsletters were a monologue
2s2
matches intent
shared field
signature-3d		hook5.0–10.0skinetic-buildicon·ember-fill♪ node_lock
You talked weekly and never learned what any single reader wanted.
on-screen: You talked, they never replied
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground blacktreatment ember-fillmotion kinetic-buildpower laser-lockinstrument laser-trace→You talked, they never replied
3s3
matches intent
NumberedList
template		teach10.0–15.7skinetic-buildicon·wireframe♪ node_lock
The move: let what a reader clicks decide the very next email they get.
on-screen: Let the click pick the next email
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let the click pick the next emailcurate items, nodes
4s4
matches intent
ComparisonTable
template		proof15.7–20.7sreceipts-counticon·white-knockout♪ node_lock
Each reader walks a path their own clicks built, not one you forced.
on-screen: Behavior writes the journey
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape dodecaground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Behavior writes the journeycurate colA, colB, rows, statsLabels
5s5
matches intent
TerminalRun
template		diff20.7–26.7scrossfade-8ficon·liquid-chrome♪ node_lock
Old way: one path for everyone. We let the data branch the path.
on-screen: We don't send one path to all
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual codeshape dodecaground blacktreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→We don't send one path to allcurate codeLines
6s6
matches intent
ChecklistCard
template		teach26.7–31.7skinetic-buildicon·ember-fill♪ node_lock
Now AI drafts the next message based on what that reader just did.
on-screen: AI drafts the branch on the fly
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→AI drafts the branch on the flycurate items, nodes
7s7
matches intent
KpiGrid
template		proof31.7–37.4sreceipts-counticon·wireframe♪ node_lock
It writes as if the list had one person, because to them it does.
on-screen: It writes a list of one
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→It writes a list of onecurate kpis, statsLabels
8s8
matches intent
FlowSchematic
template		step37.4–42.4skinetic-buildicon·white-knockout♪ node_lock
Step: start with two simple branches before you build a maze.
on-screen: Map two branches, then grow
expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual pipelineshape dodecaground blacktreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Map two branches, then growcurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve42.4–48.6scoalescenceicon·white-knockout♪ bed_out
Email that listens beats email that shouts. The Big T-M makes it listen.
on-screen: Email that listens back
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Email that listens back

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)

tiktokYour newsletter is a monologue. Let what a reader CLICKS pick their next email, so each person walks a path their own clicks built. Write a list of one. (AI-assisted) #emailmarketing #newsletter
instagramYou talked weekly, they never replied. Let the click pick the next email. Write as if the list had one person. #emailmarketing #newsletter #email #marketing #personalization
linkedinEmail newsletters used to be a monologue shouted at a silent crowd: you talked weekly and never learned what any single reader wanted. The shift is to let what a reader clicks decide the very next email they get, so each person walks a path their own clicks built, not one you forced. Instead of one path for everyone, let the data branch it, and let AI draft the next message based on what that reader just did, writing as if the list had one person, because to them it does. Start with two simple branches before you build a maze. Email that listens beats email that shouts.
xYour newsletter is a monologue. Let what a reader clicks pick their next email. temerarii.com
facebookYour newsletter talks weekly and never learns what one reader wants. Let what a reader clicks decide their next email, branch the path by behavior, and let AI write as if the list had one person. Start with two branches. Want email that listens? Visit temerarii.com.
threadsNewsletters used to be a monologue. You talked, they never replied. Let what a reader clicks pick their next email, so each person walks a path their own clicks built. Start with two branches before a maze. Email that listens beats email that shouts.
pinterestEmail personalization tips: let each reader's clicks decide the next email they receive, branch the journey by behavior instead of sending one path to everyone, use AI to draft the next message based on what they just did, and start with two simple branches. Build behavior-driven newsletter journeys that feel one-to-one.
blueskyYour newsletter is a monologue. Let what a reader clicks pick their next email. temerarii.com
youtubeTurn Your Newsletter Monologue Into A Conversation Newsletters shout at a silent crowd. Let what a reader clicks pick their next email, branch the path by behavior, and write as if the list had one person. Start with two branches. AI-assisted production. Learn personalization at temerarii.com.

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

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view