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-W36-Fri-2kind threadweek W36date 2026-09-11campaign thread · Fripillar it_devbeat Friasset videoduration 48.8sground whitescenes 9

Checklist the per-video bar — engine/sim

86.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W36-Fri-2 good|bad)
⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_sequence_across_assetsdup_set_across_assets · 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 · 48.8s · 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
Go-to-market used to be a chain of manual handoffs between five tools.
on-screen: Go-to-market meant manual handoffs
expected on screen: white 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 whitetreatment wireframemotion spatial-parallaxpower summoninstrument summon→Go-to-market meant manual handoffs
2s2
matches intent
shared field
signature-3d		hook5.0–10.5skinetic-buildicon·wireframe♪ node_lock
Leads slipped through the cracks between every tool that didn't talk to each other.
on-screen: Leads slipped through every crack
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→Leads slipped through every crack
3s3
matches intent
NumberedList
template		teach10.5–16.0skinetic-buildicon·wireframe♪ node_lock
First move: map the steps a lead takes before you automate a single one.
on-screen: Map the steps before automating
expected on screen: white 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 whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Map the steps before automatingcurate items, nodes
4s4
matches intent
RankList
template		proof16.0–21.5sreceipts-counticon·wireframe♪ node_lock
Then wire an agent to handle the boring parts, like routing and follow-up notes.
on-screen: Wire an agent for boring parts
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Wire an agent for boring partscurate rows, statsLabels
5s5
matches intent
LogStream
template		diff21.5–26.7scrossfade-8ficon·wireframe♪ node_lock
But automating a broken process only makes the mess arrive faster and louder.
on-screen: Automating a mess just speeds the mess
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual codeshape boxground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Automating a mess just speeds the messcurate codeLines, rows
6s6
matches intent
ChecklistCard
template		teach26.7–32.6skinetic-buildicon·wireframe♪ node_lock
So you keep a human on the one step that needs real judgment, every time.
on-screen: Keep a human at the real decision
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Keep a human at the real decisioncurate items, nodes
7s7
matches intent
StatScoreboard
template		proof32.6–38.1sreceipts-counticon·wireframe♪ node_lock
The robot does the repeat work, and your people spend time where it counts.
on-screen: Robots do the repeat work
expected on screen: white 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 whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Robots do the repeat workcurate pillar, stats, statsLabels
8s8
matches intent
ListCard
template		step38.1–43.6skinetic-buildicon·wireframe♪ node_lock
Try it: map one lead flow and automate just the most boring repeated step.
on-screen: Map one flow, automate one step
expected on screen: white ground · a ListCard panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual pipelineshape boxground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Map one flow, automate one stepcurate items, stages, steps
9s9
matches intent
shared field
signature-3d		resolve43.6–48.800000000000004scoalescenceicon·wireframe♪ bed_out
Soon the pipeline keeps moving while you sleep, and nothing slips the cracks.
on-screen: Soon the pipeline runs while you sleep
expected on screen: white 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 whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Soon the pipeline runs while you sleep

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)

tiktokDon't automate a broken process, you'll just speed up the mess. Here is the move (AI-assisted): map the steps a lead takes FIRST, then wire an agent to handle the boring repeat parts, and keep a human on the one real decision. #gtm #automation #aitools
instagramDon't automate a mess. Map the lead's steps first. Wire an agent for the boring parts. Keep a human on the real call. The pipeline runs while you sleep. #gtm #marketingautomation #aitools #salesops #automation
linkedinGo-to-market used to be manual handoffs between tools that didn't talk, and leads slipped through the cracks. The method: map the steps a lead takes before you automate anything, then wire an agent for the boring repeat work and keep a human on the one step that needs judgment. The takeaway: automating a broken process only speeds up the mess.
xGTM automation move: map the lead's steps first, wire an agent for the boring repeat work, keep a human on the real decision. Don't speed up a mess. temerarii.com
facebookGo-to-market used to be manual handoffs between tools that didn't talk. The method: map the lead's steps first, then wire an agent for the boring repeat work and keep a human on the real decision. Don't automate a mess. See it at temerarii.com.
threadsDon't automate a broken process, you'll just speed up the mess. Map the lead's steps first, wire an agent for the boring repeat parts, keep a human on the real call.
pinterestAI and automation for go-to-market: how to automate without speeding up a mess. Map the lead's steps first, wire an agent for repeat work, and keep a human on the real decision. Evergreen guide to GTM, marketing automation, and sales operations.
blueskyGTM automation move: map the lead's steps first, wire an agent for the boring repeat work, keep a human on the real decision. Don't speed up a mess. temerarii.com
youtubeAI Automation For Go-To-Market: Don't Speed Up A Mess Go-to-market used to be a chain of manual handoffs between five tools that didn't talk, and leads slipped through the cracks. The real method: map the steps a lead takes before you automate a single one, then wire an agent to handle the boring repeat parts like routing and follow-up notes. Automating a broken process only makes the mess arrive faster, so keep a human on the one step that needs real judgment. 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