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-3kind threadweek W23date 2026-06-11campaign thread · Thupillar it_devbeat Thuasset videoduration 50.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-3 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 · 50.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·wireframe♪ bed_in
Business reports used to live in a dozen spreadsheets nobody agreed on.
on-screen: Reports lived in scattered files
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→Reports lived in scattered files
2s2
matches intent
shared field
signature-3d		hook5.0–10.0skinetic-buildicon·ember-fill♪ node_lock
Two teams brought two numbers for the same thing to the same meeting.
on-screen: Two teams, two different truths
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground blacktreatment ember-fillmotion kinetic-buildpower laser-lockinstrument laser-trace→Two teams, two different truths
3s3
matches intent
NumberedList
template		teach10.0–16.0skinetic-buildicon·wireframe♪ node_lock
The move: pour every source into one clean store with one definition.
on-screen: Pour all data into one place
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Pour all data into one placecurate items, nodes
4s4
matches intent
RankList
template		proof16.0–21.6sreceipts-counticon·white-knockout♪ node_lock
When everyone reads the same number, the meeting argues about action, not math.
on-screen: One definition ends the argument
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→One definition ends the argumentcurate rows, statsLabels
5s5
matches intent
DiffCard
template		diff21.6–28.1scrossfade-8ficon·liquid-chrome♪ node_lock
Old way: email a spreadsheet around. We point everyone at one live view.
on-screen: We don't email spreadsheets
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual codeshape boxground blacktreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→We don't email spreadsheetscurate codeLines, lines
6s6
matches intent
ChecklistCard
template		teach28.1–33.1skinetic-buildicon·ember-fill♪ node_lock
Now AI reads the spike and writes the plain reason behind it.
on-screen: AI explains the weird spike
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→AI explains the weird spikecurate items, nodes
7s7
matches intent
StatScoreboard
template		proof33.1–38.7sreceipts-counticon·wireframe♪ node_lock
You ask in plain words and it answers in plain words, not formulas.
on-screen: It answers in plain sentences
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→It answers in plain sentencescurate pillar, stats, statsLabels
8s8
matches intent
NodeGraphCard
template		step38.7–44.800000000000004skinetic-buildicon·white-knockout♪ node_lock
Step: write down what each metric means once, so nobody redefines it.
on-screen: Agree on the metric once
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual pipelineshape boxground blacktreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Agree on the metric oncecurate hub, nodes, stages, steps
9s9
matches intent
shared field
signature-3d		resolve44.8–50.599999999999994scoalescenceicon·wireframe♪ bed_out
One number everyone trusts ends the war. The Big T-M builds that store.
on-screen: One number everyone trusts
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→One number everyone trusts

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)

tiktokTwo teams, two different numbers for the same thing? Pour every source into one store with ONE definition. Then meetings argue about action, not math. (AI-assisted) #businessintelligence #data
instagramReports lived in a dozen spreadsheets. Pour every source into one store, one definition. Ask in plain words, get a plain answer. #businessintelligence #data #analytics #bi #dashboard
linkedinBusiness reports used to live in a dozen spreadsheets nobody agreed on, so two teams brought two numbers for the same thing to the same meeting. The fix: pour every source into one clean store with one definition, because when everyone reads the same number, the meeting argues about action, not math. Instead of emailing spreadsheets around, point everyone at one live view, and let AI read a weird spike and write the plain reason behind it. Agree once on what each metric means so nobody redefines it. One number everyone trusts ends the war.
xTwo teams, two numbers for the same thing? Pour every source into one store with one definition. temerarii.com
facebookTwo teams bring two numbers for the same thing to the same meeting. Pour every source into one clean store with one definition, point everyone at one live view, and let AI explain the weird spike in plain words. Want one number everyone trusts? Visit temerarii.com.
threadsTwo teams, two different truths for the same metric. Pour every source into one store with one definition, point everyone at one live view, and let AI explain the spike in plain words. One number everyone trusts ends the war.
pinterestBusiness intelligence tips: pour every data source into one clean store with a single agreed definition for each metric, point the whole team at one live dashboard instead of emailing spreadsheets, and use AI to explain spikes in plain language. End the meeting where two teams bring two different numbers.
blueskyTwo teams, two numbers for the same thing? Pour every source into one store with one definition. temerarii.com
youtubeEnd The Two-Numbers Meeting: One Store, One Definition Reports in a dozen spreadsheets mean two teams bring two truths. Pour every source into one store with one definition, point everyone at one live view, and let AI explain the spike. AI-assisted production. Learn more 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