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-W25-Thu-2kind threadweek W25date 2026-06-25campaign thread · Thupillar staff_trainingbeat Thuasset videoduration 49.1sground whitescenes 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-W25-Thu-2 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 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 · 49.1s · 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·3d-extrude♪ bed_in
The old way ran go-to-market by hand, copying leads between ten tabs.
on-screen: Go-to-market used to be all manual
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground whitetreatment 3d-extrudemotion spatial-parallaxpower summoninstrument summon→Go-to-market used to be all manual
2s2
matches intent
shared field
signature-3d
hook5.0–10.2skinetic-buildicon·wireframe♪ node_lock
Here is where it goes: the boring steps run themselves while you decide.
on-screen: Soon the boring steps run themselves
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→Soon the boring steps run themselves
3s3
matches intent
NumberedList
template
teach10.2–15.7skinetic-buildicon·wireframe♪ node_lock
Write each step as a plain rule a model can follow without you watching.
on-screen: Write each step as a clear rule
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write each step as a clear rulecurate items, nodes
4s4
matches intent
ComparisonTable
template
proof15.7–22.0sreceipts-counticon·wireframe♪ node_lock
A new lead comes in, the model reads it and routes it to the right place.
on-screen: New lead in, the model routes it
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape knotground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→New lead in, the model routes itcurate colA, colB, rows, statsLabels
5s5
matches intent
StackTrace
template
diff22.0–27.0scrossfade-8ficon·wireframe♪ node_lock
You automate the rote work and keep the judgment calls for yourself.
on-screen: Automate the rote, keep the judgment
expected on screen: white ground · a StackTrace panel over a dimmed Signal Field · Magister leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual codeshape knotground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Automate the rote, keep the judgmentcurate codeLines, errMsg, errType, fix, frames
6s6
matches intent
ChecklistCard
template
teach27.0–32.5skinetic-buildicon·wireframe♪ node_lock
Let the model draft the first reply, then you approve or fix one line.
on-screen: Let AI draft the first reply
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let AI draft the first replycurate items, nodes
7s7
matches intent
KpiGrid
template
proof32.5–37.7sreceipts-counticon·wireframe♪ node_lock
Drafts wait for your yes, so the work moves without you starting it.
on-screen: Drafts ready; you just say yes
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape knotground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Drafts ready; you just say yescurate kpis, statsLabels
8s8
matches intent
StepFlow
template
step37.7–43.6skinetic-buildicon·wireframe♪ node_lock
List your steps, turn each into a rule, keep an approval on the risky ones.
on-screen: List steps, rule them, keep approval
expected on screen: white ground · a StepFlow panel over a dimmed Signal Field · Magister leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual pipelineshape knotground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→List steps, rule them, keep approvalcurate stages, steps
9s9
matches intent
shared field
signature-3d
resolve43.6–49.1scoalescenceicon·3d-extrude♪ bed_out
The Big T-M automates the rote and keeps the human call where it matters.
on-screen: The Big T-M automates the rote
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→The Big T-M automates the rote

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)

tiktokWhere go-to-market is heading (AI-assisted): write each boring step as a plain rule a model can run. New lead comes in, it routes and drafts the first reply. You keep the judgment calls. #gtm #automation #aiautomation
instagramAutomate the boring steps. Keep the judgment calls. Write each step as a rule. #gtm #automation #aiforbusiness #marketing #sales
linkedinGo-to-market runs on too much manual work. The coming method: write each rote step as a plain rule a model can follow, so a new lead gets read, routed, and given a drafted first reply. The takeaway: automate the rote, keep the judgment. Hold an approval step on anything risky, and the work moves without you starting it.
xGTM is heading toward rules a model runs: lead comes in, it routes and drafts the reply. Automate rote, keep the judgment. temerarii.xyz
facebookRunning go-to-market by hand means copying leads between ten tabs. The shift coming: write each boring step as a rule a model can run, so it routes leads and drafts replies. You keep the judgment calls. See how on the site.
threadsSoon the boring GTM steps run themselves. Write each step as a plain rule, let a model route leads and draft first replies, and keep the judgment calls and approvals for yourself.
pinterestAI go-to-market automation: write each rote step as a plain rule a model can run, so leads get routed and replies get drafted. Automate the boring work, keep the judgment. GTM strategy, marketing automation, AI for business.
blueskyGTM is heading toward rules a model runs: it routes leads and drafts replies. Automate rote, keep judgment. temerarii.xyz
youtubeAutomate the Boring GTM Steps, Keep the Judgment Go-to-market runs on too much manual work. We walk through the coming method: write each rote step as a plain rule a model can follow, so a new lead gets read, routed, and given a drafted first reply. Automate the rote, keep the judgment calls, and hold an approval step on anything risky.

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