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 longform-W50-Thukind longformweek W50date 2026-12-17campaign longform-youtubepillar performancebeat asset videoduration 192.2sground blackscenes 8

Checklist the per-video bar — engine/sim

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

Composition comp · template family · expected output

composition LongFormChaptersfamily / template LongFormChapters
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 8 scenes · 192.2s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–24.5sspatial-parallaxicon·wireframe♪ bed_in
Today is AI and automation for go-to-market, and we go past asking a chatbot. We build your team a small worker that does one full job on its own. By the end you will have an agent that takes a new lead and gets it ready for a human, hands-free. Open the workspace. We start by picking the one job worth automating, because not every job is.
on-screen: Build your own AI worker
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→Build your own AI worker
2s2
matches intent
NumberedList
template
teach24.5–48.6skinetic-buildicon·ember-fill♪ node_lock
First move: choose the right task. The best one is boring, frequent, and done the same way every time. Sorting new leads, writing a first reply, logging a deal. We have your team list their weekly chores and circle the one that never changes. If a task needs real judgment every time, leave it human. The model is for the parts that are always the same.
on-screen: Pick a job done the same way
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Pick a job done the same waycurate items, nodes
3s3
matches intent
ChecklistCard
template
teach48.6–72.0skinetic-buildicon·wireframe♪ node_lock
Second move: write the job as steps a child could follow. When a lead comes in, read these fields, look up the company, draft a reply in our voice, save it as a draft, never send. Your team writes this list in plain English. The agent only needs an ordered recipe. Most automation fails because the steps lived in someone's head, not on paper.
on-screen: Write the steps in order
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write the steps in ordercurate items, nodes
4s4
matches intent
CodeWindow
template
teach72.0–96.1skinetic-buildicon·white-knockout♪ node_lock
Third move: give it the tools through MCP servers. The agent needs to read your form, look up the company, and write a draft email, so we connect each one. Now it can actually do the steps, not just describe them. Your team watches it run end to end on one test lead, and they see exactly which tool it touches at each move. Nothing hidden.
on-screen: Connect the tools it needs
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual node-graphshape dodecaground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Connect the tools it needscurate codeLines, nodes, windowTitle
5s5
matches intent
BuildLog
template
teach96.1–121.3skinetic-buildicon·liquid-chrome♪ node_lock
Fourth move: keep a human at the gate. We set one hard rule. The agent drafts, a person sends. It can do ninety percent of the work, the reading and the typing, but it stops before anything goes out the door. Your team reviews the draft, fixes a line, and hits send. That gate is how you get the speed without the risk of a bad message going out.
on-screen: Always draft, never send
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual node-graphshape dodecaground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Always draft, never sendcurate lines, nodes
6s6
first render · fix pending
DiffCard
templatecustom_element_dup
teach121.3–145.1skinetic-buildicon·ember-fill♪ node_lock
Fifth move: let it run without you. We put the agent on a simple schedule or a trigger, so it wakes up when a new lead arrives, does its steps, and leaves a draft waiting. Your team comes in to a stack of ready replies instead of a blank inbox. The work happened while nobody was watching, and a person still made the final call.
on-screen: Run it on a schedule
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual node-graphshape dodecaground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Run it on a schedulecurate lines, nodes
7s7
matches intent
KpiGrid
template
proof145.1–169.2sreceipts-counticon·wireframe♪ node_lock
Honest proof: The Big T-M runs its own studio on agents exactly like this. One brain in the terminal, every tool wired in through MCP, building and checking work on a schedule, with a human approving the important steps. We are handing you the same setup we trust with our own name. It runs in public, so you never have to take our word for it.
on-screen: Our studio runs this way
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→Our studio runs this waycurate kpis, statsLabels
8s8
matches intent
shared field
signature-3d
resolve169.2–192.2scoalescenceicon·wireframe♪ bed_out
The takeaway: an AI worker is just a clear job, the right tools, and a human at the gate. Build one, trust it, then build the next. Your team now has a working agent and the recipe to make more. See the whole studio running at office dot temerarii dot xyz, and tomorrow we put your numbers on a screen everyone can read.
on-screen: One worker, then the next
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→One worker, then the next

Format stack 1 aspects · same scenes[], re-cropped

16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 2 destinations

YouTubeBlog

Social captions supplemental published copy · per channel (comp_id level)

youtubeBuild an AI worker that preps every new lead, hands-free This goes past asking a chatbot. We build your team a small worker that does one full job on its own: it takes a new lead and gets it ready for a human, hands-free. The moves: - Pick a job done the same way. The best task is boring, frequent, and done the same way every time. Sorting new leads, writing a first reply, logging a deal. If a task needs real judgment every time, leave it human. The model is for the parts that are always the same. - Write the steps in order. When a lead comes in, read these fields, look up the company, draft a reply in our voice, save it as a draft, never send. Write this list in plain English. Most automation fails because the steps lived in someone's head, not on paper. - Connect the tools it needs. Give it the form, the lookup, and the draft email through MCP servers, so it can actually do the steps, not just describe them. Watch it run end to end on one test lead and see exactly which tool it touches at each move. - Always draft, never send. One hard rule: the agent drafts, a person sends. It can do most of the work, the reading and the typing, but it stops before anything goes out the door. That gate gives you speed without the risk of a bad message going out. - Run it on a schedule. Put the agent on a simple schedule or a trigger, so it wakes when a new lead arrives, does its steps, and leaves a draft waiting. You come in to a stack of ready replies instead of a blank inbox. The honest proof: we run our own studio on agents exactly like this. One brain in the terminal, every tool wired in through MCP, building and checking work on a schedule, with a human approving the important steps. It runs in public, so you never have to take our word. An AI worker is just a clear job, the right tools, and a human at the gate. See the whole studio at office.temerarii.xyz Keywords: AI agent for lead handling, MCP tools, human in the loop, draft never send, scheduled automation, sales workflow

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