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-W52-Sunkind longformweek W52date 2026-12-27campaign longform-youtubepillar strategic_relationsbeat asset videoduration 248.5sground redscenes 10

Checklist the per-video bar — engine/sim

98.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W52-Sun 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 10 scenes · 248.5s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–26.6sspatial-parallaxicon·liquid-chrome♪ bed_in
This week the calendar says one thing: explore what is next. So we will. Today we open up the part everyone is loudest about and clearest on least, plain old artificial intelligence, and we show you the actual moves we run at The Big T-M instead of the empty hype words everyone reaches for. By the end you will know how to point a real model at a real job, not a demo.
on-screen: What is next is already here
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→What is next is already here
2s2
matches intent
NumberedList
template
teach26.6–52.1skinetic-buildicon·white-knockout♪ node_lock
First move. Stop asking which model is best and start asking what the task needs. A short rewrite job needs a small fast model. A long planning job needs one that holds a lot in its head at once. We keep a tiny note that maps each job to a model and a price, and we read it before we call anything. The job picks the model, not the headline.
on-screen: Pick the model by the job
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Pick the model by the jobcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach52.1–79.4skinetic-buildicon·liquid-chrome♪ node_lock
Second move. A model reads a prompt the way a new hire reads a brief. So write it like one. Give the role, the goal, the format you want back, and one example of good output. We keep our prompts in plain text files in the repo, not buried in a chat window, so we can edit them, diff them, and reuse them. A saved prompt is a tool. A typed one is a guess.
on-screen: Write the prompt like a brief
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Write the prompt like a briefcurate items, nodes
4s4
matches intent
DiffCard
template
teach79.4–103.5skinetic-buildicon·white-knockout♪ node_lock
Third move. A model only knows the world up to a point, and it knows nothing about you. So hand it your own pages, your own docs, your own numbers, inside the prompt. We pull our content straight off disk and paste the relevant slice in. No fine-tuning, no training run. Just give it the facts it needs in the same message you ask the question.
on-screen: Feed it your own data
expected on screen: red ground · a DiffCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Feed it your own datacurate lines, nodes
5s5
matches intent
CodeWindow
template
teach103.5–127.6skinetic-buildicon·liquid-chrome♪ node_lock
Fourth move. The model gets useful when it can act, not just talk. We wire it to tools through MCP, small adapters that let one agent reach a calendar, a file, a search index, a database. You describe each tool once in plain words. Then the model decides when to reach for it. That is the jump from a chatbot to something that does the work.
on-screen: Let it call your tools
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Let it call your toolscurate codeLines, nodes, windowTitle
6s6
matches intent
WireframeMock
template
teach127.6–150.29999999999998skinetic-buildicon·white-knockout♪ node_lock
Fifth move. Ask the model to lay out its plan before it acts, in numbered steps. Then read the steps. Most bad answers come from a bad plan you never saw. When the plan is on the table you can stop it at step two instead of cleaning up at step ten. We make every agent print the plan first. Cheap insurance.
on-screen: Make it show its steps
expected on screen: red ground · a WireframeMock panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Make it show its stepscurate nodes
7s7
matches intent
StepFlow
template
teach150.3–174.4skinetic-buildicon·liquid-chrome♪ node_lock
Sixth move. Never trust one model alone on anything that ships. We run the output back through a second pass with a fresh prompt that only asks one thing: find what is wrong here. A model is a harsh editor of work it did not write. Two passes, one to make and one to break, and the junk falls out before a human ever sees it.
on-screen: Check the work with a second model
expected on screen: red ground · a StepFlow panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Check the work with a second modelcurate nodes, steps
8s8
first render · fix pending
BlueprintGrid
templatecustom_element_dup
teach174.4–196.70000000000002skinetic-buildicon·white-knockout♪ node_lock
Seventh move. Automate the boring middle, keep a person at the door. The model drafts, checks, and stacks the work up. A human says ship or no. We never let an agent post, pay, or send on its own. The point is to delete the busywork between idea and decision, not to delete the decision. That line is where trust lives.
on-screen: Keep a human at the gate
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Keep a human at the gatecurate nodes, rows
9s9
matches intent
KpiGrid
template
proof196.7–220.79999999999998sreceipts-counticon·liquid-chrome♪ node_lock
Here is the proof, and there are no invented numbers in it. The whole campaign you are watching, the videos, the articles, the calendar, was built from one source file by an agent running these exact moves. We did not write a press kit about AI. We pointed it at our own studio and let it run in public. You can watch it work at office.temerarii.xyz.
on-screen: We run our own studio on this
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We run our own studio on thiscurate kpis, statsLabels
10s10
matches intent
shared field
signature-3d
resolve220.8–248.5scoalescenceicon·liquid-chrome♪ bed_out
So that is the takeaway. AI is not a wave to ride, it is a set of moves you can name and repeat. Pick one job you hate doing, write the prompt like a brief, feed it your own data, and check it twice. Do that one job well, then add the next. The next thing is not coming. It is sitting in your terminal waiting for a clear instruction. See the whole machine at office.temerarii.xyz.
on-screen: Start with one job today
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→Start with one job today

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)

youtubeAI for real work: the seven moves we run to point a model at a real job We open the part everyone is loudest about and clearest on least, plain artificial intelligence, and show the actual moves we run instead of empty hype words. By the end you will know how to point a real model at a real job, not a demo. The moves: - Pick the model by the job. Stop asking which model is best and start asking what the task needs. A short rewrite needs a small fast model; a long planning job needs one that holds a lot at once. Keep a tiny note that maps each job to a model and a price, and read it before you call anything. - Write the prompt like a brief. A model reads a prompt the way a new hire reads a brief. Give the role, the goal, the format you want back, and one example of good output. Keep prompts in plain text files in the repo, not buried in a chat window, so you can edit, diff, and reuse them. - Feed it your own data. A model knows nothing about you. Hand it your own pages, docs, and numbers inside the prompt. No fine-tuning, no training run. Just give it the facts it needs in the same message you ask the question. - Let it call your tools. The model gets useful when it can act, not just talk. Wire it to tools through MCP, small adapters that let one agent reach a calendar, a file, a search index, a database. You describe each tool once; the model decides when to reach for it. - Make it show its steps. Ask the model to lay out its plan before it acts, in numbered steps, then read the steps. Most bad answers come from a bad plan you never saw. When the plan is on the table you can stop it at step two instead of cleaning up at step ten. - Check the work with a second model. Never trust one model alone on anything that ships. Run the output back through a second pass with a fresh prompt that only asks: find what is wrong here. Two passes, one to make and one to break, and the junk falls out before a human sees it. - Keep a human at the gate. Automate the boring middle, keep a person at the door. The model drafts, checks, and stacks the work up; a human says ship or no. We never let an agent post, pay, or send on its own. The proof, no invented numbers: the whole campaign you are watching, the videos, the articles, the calendar, was built from one source file by an agent running these exact moves. We pointed it at our own studio and let it run in public. AI is not a wave to ride; it is a set of moves you can name and repeat. Pick one job you hate, write the prompt like a brief, feed it your own data, and check it twice. See the whole machine at office.temerarii.xyz Keywords: practical AI, model routing, prompt as a brief, feed your own data, MCP tools, show the plan, second-model check, human in the loop

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