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-W49-Tuekind longformweek W49date 2026-12-08campaign longform-youtubepillar socialbeat —asset videoduration 154.6sground blackscenes 8

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-W49-Tue 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 8 scenes · 154.6s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–22.3sspatial-parallaxicon·ember-fill♪ bed_in
This week is about the operating layer, and nothing sums it up like this: run it. Today we open automated workflows, the part that does the dull, repeated jobs while you sleep. By the end you will know how to turn a task you do by hand every week into a step the machine runs by itself, on time, every time.
on-screen: Kill the busywork
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape torusground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Kill the busywork
2s2
matches intent
NumberedList
template		teach22.3–43.2skinetic-buildicon·wireframe♪ node_lock
The first move is to write the task as a list of steps, like a recipe. Open this, copy that, paste it there, send the email. If you cannot say the steps in plain words, you cannot hand them to a machine. So say them. The recipe is the work, the code is just typing it up.
on-screen: Name the task out loud
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Name the task out loudcurate items, nodes
3s3
matches intent
ChecklistCard
template		teach43.2–63.0skinetic-buildicon·wireframe♪ node_lock
The second move is to connect the agent to the apps in your recipe through MCP servers. Your inbox, your sheet, your storage. Now when the recipe says send the email, the agent actually sends it through the real tool, not a pretend one. Each step in the recipe maps to one tool call.
on-screen: Give the agent the real tools
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Give the agent the real toolscurate items, nodes
4s4
matches intent
StepFlow
template		teach63.0–81.4skinetic-buildicon·wireframe♪ node_lock
The third move is to give it a trigger. A schedule, like every Monday at eight, set with a plain cron line. Or an event, like a new row in a sheet. The trigger is what makes it run without you remembering. You set the clock once and walk away.
on-screen: Put it on a clock
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Put it on a clockcurate nodes, steps
5s5
matches intent
AnnotatedDiagram
template		teach81.4–101.9skinetic-buildicon·wireframe♪ node_lock
The fourth move keeps it honest. Make the workflow write down what it did each time, and run it once in dry-run mode where it shows the steps but changes nothing. You read the log, confirm it would have done the right thing, then let it loose. Trust the machine after you watch it, not before.
on-screen: Log every run, dry-run first
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Log every run, dry-run firstcurate callouts, nodes
6s6
matches intent
ListCard
template		teach101.9–118.9skinetic-buildicon·wireframe♪ node_lock
Here is the proof, no invented numbers. The whole content calendar you are watching, including this video, is fanned out and scheduled by automated workflows from one source file. We wrote the recipe once. The studio runs it on a clock while we do other work.
on-screen: Our calendar posts itself
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual node-graphshape torusground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Our calendar posts itselfcurate items, nodes
7s7
matches intent
ComparisonTable
template		proof118.9–136.6sreceipts-counticon·wireframe♪ node_lock
So an automated workflow is just a recipe, plus real tools, plus a clock, plus a log. Once it works, the boring job is gone for good, not just for today. Tomorrow we look at the machine that all this runs on and how to keep it healthy.
on-screen: Boring jobs, gone for good
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape torusground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Boring jobs, gone for goodcurate colA, colB, rows, statsLabels
8s8
matches intent
shared field
signature-3d		resolve136.6–154.6scoalescenceicon·ember-fill♪ bed_out
That is the heart of running it: let the machine carry the repeat work so your hours go to the work only a person can do. Go to office.temerarii.xyz and look at the calendar. Every cell on it was placed by a workflow you could build the same way.
on-screen: Watch it run at office.temerarii.xyz
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Watch it run at office.temerarii.xyz

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)

youtubeAutomated workflows: turn a weekly chore into a step the machine runs Automated workflows do the dull, repeated jobs while you sleep. This video shows how to turn a task you do by hand every week into a step the machine runs by itself, on time, every time. The four moves: - Name the task out loud. Write the task as a list of steps, like a recipe. Open this, copy that, paste it there, send the email. If you cannot say the steps in plain words, you cannot hand them to a machine. The recipe is the work; the code is just typing it up. - Give the agent the real tools. Connect the agent to the apps in your recipe through MCP servers: your inbox, your sheet, your storage. When the recipe says send the email, the agent sends it through the real tool, not a pretend one. Each step maps to one tool call. - Put it on a clock. Give it a trigger. A schedule, like every Monday at eight, set with a plain cron line. Or an event, like a new row in a sheet. The trigger is what makes it run without you remembering. Set the clock once and walk away. - Log every run, dry-run first. Make the workflow write down what it did each time, and run it once in dry-run mode where it shows the steps but changes nothing. Read the log, confirm it would have done the right thing, then let it loose. Trust the machine after you watch it, not before. The proof, no invented numbers: the whole content calendar you are watching, including this video, is fanned out and scheduled by automated workflows from one source file. We wrote the recipe once. The studio runs it on a clock while we do other work. Go to office.temerarii.xyz and look at the calendar. Every cell was placed by a workflow you could build the same way. Keywords: automated workflows, cron scheduling, MCP tool calls, dry run, workflow automation for small business, recipe-based automation

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

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view