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-W37-Wed-1kind threadweek W37date 2026-09-16campaign thread · Wedpillar strategic_relationsbeat Wedasset videoduration 60.0sground redscenes 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-W37-Wed-1 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 · 60.0s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–6.3sspatial-parallaxicon·liquid-chrome♪ bed_in
We all used to lose mornings to the same clicks: copy this, paste there, send, repeat.
on-screen: Busywork ate the whole morning
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Busywork ate the whole morning
2s2
matches intent
shared field
signature-3d
hook6.3–13.3skinetic-buildicon·white-knockout♪ node_lock
Here is the rule: if a person does the same steps daily, that job belongs to a machine.
on-screen: If a human repeats it, automate it
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→If a human repeats it, automate it
3s3
matches intent
NumberedList
template
teach13.3–21.700000000000003skinetic-buildicon·liquid-chrome♪ node_lock
So we do it now with AI: first map the exact steps a human takes, then hand each one to a tool.
on-screen: Map the steps before you build
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Map the steps before you buildcurate items, nodes
4s4
matches intent
RankList
template
proof21.7–28.299999999999997sreceipts-counticon·white-knockout♪ node_lock
A clean workflow is just a trigger, a few actions, and a check that it actually worked.
on-screen: Trigger, action, check, done
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape tetraground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Trigger, action, check, donecurate rows, statsLabels
5s5
matches intent
BuildLog
template
diff28.3–34.6scrossfade-8ficon·liquid-chrome♪ node_lock
The old way used a person as the glue between five apps that refused to talk.
on-screen: Old way: a person as the glue
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual codeshape tetraground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Old way: a person as the gluecurate codeLines, lines
6s6
matches intent
ChecklistCard
template
teach34.6–41.2skinetic-buildicon·white-knockout♪ node_lock
Now AI can handle the fuzzy steps too, reading a message and deciding where it should go.
on-screen: Now AI handles the judgment steps
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Now AI handles the judgment stepscurate items, nodes
7s7
matches intent
StatScoreboard
template
proof41.2–47.800000000000004sreceipts-counticon·liquid-chrome♪ node_lock
Automation frees the person for the calls that need a human, not the clicks that never did.
on-screen: Free the human for the hard calls
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Free the human for the hard callscurate pillar, stats, statsLabels
8s8
matches intent
AnnotatedDiagram
template
step47.8–54.8skinetic-buildicon·white-knockout♪ node_lock
Your move: map the repeat task, set a trigger, automate each step, add a check at the end.
on-screen: Steps: map, trigger, automate, verify
expected on screen: red ground · a AnnotatedDiagram panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual pipelineshape tetraground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Steps: map, trigger, automate, verifycurate callouts, stages, steps
9s9
matches intent
shared field
signature-3d
resolve54.8–60.0scoalescenceicon·liquid-chrome♪ bed_out
That is how The Big T-M lets machines do the boring part, well.
on-screen: Let machines do the boring part
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Let machines do the boring part

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)

tiktokAutomation rule: if a human does the same steps every day, that's a machine's job. Map the exact steps first, then hand each one to a tool, trigger, actions, check. AI handles the judgment steps now. AI-assisted. #automation #workflow #productivity #nocode #tech
instagramSame steps daily? That's a machine's job. Map it, then automate it. #automation #workflow #productivity #nocode #tech
linkedinThe test for automation is simple: if a person repeats the same steps daily, that work belongs to a machine. The method: map the exact steps a human takes first, then hand each to a tool, structured as a trigger, a few actions, and a check that confirms it worked. AI can now handle the fuzzy judgment steps too, like reading a message and routing it. Automation should free people for the calls that need a human, not the clicks that never did.
xAutomation rule: if a human repeats the same steps daily, it's a machine's job. Map the steps, set a trigger, automate, add a check. temerarii.com
facebookStop losing mornings to copy-paste-send-repeat. If a person does the same steps daily, that's a machine's job. Map the steps, set a trigger, automate each one, add a check. AI handles the judgment steps now. More at temerarii.com.
threadsAutomation rule: if a human repeats the same steps every day, that's a machine's job. Map the exact steps first, then hand each to a tool, trigger, actions, check. AI now handles the fuzzy steps too. Free the person for the hard calls.
pinterestWorkflow automation method: if a task repeats daily, map the steps and automate with a trigger, actions, and a check. AI handles judgment steps. Automation tips, productivity workflows, no-code automation.
blueskyAutomation rule: if a human repeats the same steps daily, it's a machine's job. Map the steps, trigger, automate, verify. AI handles judgment now. temerarii.com
youtubeThe Automation Rule: If a Human Repeats It Daily, Automate It We cover the practical method for workflow automation: map the exact steps a person takes, structure them as a trigger, actions, and a check, and let AI handle the fuzzy judgment steps. Free people for the calls that need a human. AI-assisted. More at temerarii.com. #Automation #Workflow #Productivity

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