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-Sunkind longformweek W50date 2026-12-13campaign longform-youtubepillar multimediabeat asset videoduration 256.9sground whitescenes 10

Checklist the per-video bar — engine/sim

100.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W50-Sun good|bad)
✓ all static checks pass — one-focal/scene · tier-by-beat · one-track caption · colorway · cast+shape correct · no banned/fabricated. (audio + visual tiers verify on the rendered finals — Phase 2)

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 · 256.9s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–28.0sspatial-parallaxicon·wireframe♪ bed_in
Most training is a slideshow and a snack. You sit, you nod, you forget. This week is the opposite. We teach by handing your team the real tools and letting them ship something live by the end of the day. This first session is the map. We are going to wire AI and automation into your go-to-market work, step by step, so you can run it yourselves after we leave. No mystery, no hype, just the moves.
on-screen: Learn by doing, not watching
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground whitetreatment wireframemotion spatial-parallaxpower summoninstrument summon→Learn by doing, not watching
2s2
matches intent
NumberedList
template
teach28.0–54.6skinetic-buildicon·color♪ node_lock
Step one is the workspace. We open Claude Code in the terminal on your own laptop. It is a coding agent that holds your whole project in its head, so nobody is jumping between twelve browser tabs. Your team types what they want in plain English, and the model does the clicking. The first lab is just this: get it installed and ask it to read your folder of marketing files out loud.
on-screen: Start in the terminal
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Start in the terminalcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach54.6–81.9skinetic-buildicon·color♪ node_lock
Step two is giving the agent hands. We connect one tool through an MCP server, which is a small adapter that lets the model talk to outside software. We pick Google Sheets first because everyone has a messy sheet. Now your team can say, read my campaign tracker, and the agent pulls the rows directly. They watch the connection light up. That is the moment it stops being a chatbot and starts being a worker.
on-screen: Plug in one tool with MCP
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Plug in one tool with MCPcurate items, nodes
4s4
matches intent
NodeGraphCard
template
teach81.9–107.80000000000001skinetic-buildicon·color♪ node_lock
Step three is the prompt. We teach your team to write it like a cooking recipe, not a wish. Name the input, name the steps, name the output. Bad: make this better. Good: take these three subject lines, rewrite each in plain language under nine words, keep the offer. The lab here is each person rewrites their own vague ask into a clear one, then runs both and sees the difference.
on-screen: Write the prompt as a recipe
expected on screen: white ground · a NodeGraphCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Write the prompt as a recipecurate hub, nodes
5s5
matches intent
FlowSchematic
template
teach107.8–133.0skinetic-buildicon·color♪ node_lock
Step four is offloading busywork. We point the agent at a real chore your team hates. Tagging two hundred leads by industry. We show them how to give the model the list, the rules, and one example, then let it tag the rest. They check ten by hand to trust it. That habit, spot-check before you ship, is the whole game. The model is fast, you are the editor.
on-screen: Let the model do the boring part
expected on screen: white ground · a FlowSchematic panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Let the model do the boring partcurate nodes, stages
6s6
matches intent
AnnotatedDiagram
template
teach133.0–158.2skinetic-buildicon·color♪ node_lock
Step five is data. We connect the agent to your analytics through another MCP server and have your team ask it questions in words. Which posts brought traffic last month. Which email got opened. No more waiting on a report. They pull their own answer, see the query the model wrote, and learn to read it. Now the data lives where the decision happens, not in someone else's inbox.
on-screen: Pull your own numbers
expected on screen: white ground · a AnnotatedDiagram panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Pull your own numberscurate callouts, nodes
7s7
matches intent
LogStream
template
teach158.2–183.39999999999998skinetic-buildicon·color♪ node_lock
Step six joins the last two. Once the agent can read your numbers, we have it write from them. It looks at which topics actually pulled people in, then drafts the next three posts about those topics. Your team is not staring at a blank page anymore. They are editing a draft that already knows what worked. The lab is one post, start to finish, built off real traffic.
on-screen: Make it write from the data
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Make it write from the datacurate nodes, rows
8s8
matches intent
ListCard
template
teach183.4–207.20000000000002skinetic-buildicon·color♪ node_lock
Step seven is making it stick. A good prompt should not die when the person closes the laptop. We teach your team to save each working recipe as a small file in the project, so anyone can run it again next week. This is how a workshop becomes a system. One person figures out the lead-tagging move once, and the whole team inherits it forever.
on-screen: Save the move, reuse it
expected on screen: white ground · a ListCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Save the move, reuse itcurate items, nodes
9s9
matches intent
ComparisonTable
template
proof207.2–232.39999999999998sreceipts-counticon·color♪ node_lock
Here is our proof, with no invented numbers. The Big T-M runs its own studio on exactly these moves. Our whole content calendar, every video and post, is built by an AI agent from one source file. We are not selling you a method we read about. We are handing you the one we use to keep our own lights on, and you can watch it run in public.
on-screen: We built this on ourselves
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→We built this on ourselvescurate colA, colB, rows, statsLabels
10s10
matches intent
shared field
signature-3d
resolve232.4–256.9scoalescenceicon·wireframe♪ bed_out
So that is the week ahead. Each day we go deeper into one part: growth, content, data, then the automation that ties them together. The takeaway today is simple. AI is not a robot that replaces your team. It is a fast hand your team learns to direct. Go see the whole thing running at office dot temerarii dot xyz, then come back tomorrow and we build.
on-screen: See it live, then try it
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→See it live, then try it

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 go-to-market: the full map, taught by shipping live Most training is a slideshow and a snack. You sit, you nod, you forget. This is the opposite. We hand your team the real tools and ship something live by the end of the day. This session is the map of wiring AI and automation into your go-to-market work. The path, step by step: - Start in the terminal. Open Claude Code on your own laptop. It holds your whole project in its head, so nobody jumps between twelve tabs. You type what you want in plain English; the model does the clicking. - Plug in one tool with MCP. Connect one tool through an MCP server, a small adapter that lets the model talk to outside software. Google Sheets first, because everyone has a messy sheet. Now you say read my campaign tracker and the agent pulls the rows. That is when it stops being a chatbot and starts being a worker. - Write the prompt as a recipe. Name the input, the steps, and the output. Bad: make this better. Good: take these three subject lines, rewrite each in plain language under nine words, keep the offer. - Let the model do the boring part. Point it at a chore you hate, like tagging two hundred leads by industry. Give it the list, the rules, and one example, then check ten by hand to trust it. Spot-check before you ship is the whole game. - Pull your own numbers. Connect the agent to your analytics and ask questions in words: which posts brought traffic, which email got opened. The data now lives where the decision happens. - Make it write from the data. Once it can read your numbers, have it draft the next three posts about the topics that actually pulled people in. You are editing a draft that already knows what worked. - Save the move, reuse it. Save each working recipe as a small file in the project, so anyone can run it again next week. That is how a workshop becomes a system. The proof, no invented numbers: our whole content calendar, every video and post, is built by an AI agent from one source file. We hand you the method we use to keep our own lights on. AI is not a robot that replaces your team. It is a fast hand your team learns to direct. See the whole thing running at office.temerarii.xyz Keywords: AI for go-to-market, Claude Code, MCP servers, prompt as recipe, spot-check, reusable prompts, marketing automation training

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