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 topic-x-ai-automationkind topicweek —date —campaign it-dev-pillarpillar it_devbeat —asset videoduration 124.5sground blackscenes 19

Checklist the per-video bar — engine/sim

99.1/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-x-ai-automation good|bad)
⚠ 1 flag(s) — not yet ship-ready: dead_air · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SceneReel
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 19 scenes · 124.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–7.9sspatial-parallaxicon·ember-fill♪ —
Most of your work isn't creative, it's the same handoffs over and over. That part can run itself, and we'll show you exactly how.
on-screen: Automate the boring 80%
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→three-mark
2s2
matches intent
LogStream
template		legacy7.9–14.9scrossfade-8ficon·ember-fill♪ —
The old way put a person between every app, copying from one tab into another all day, the human as duct tape.
on-screen: Old way: humans as glue
expected on screen: black ground · a LogStream panel over a dimmed Signal Field · Faber leads · crossfade-8f · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id LogStreamshape boxground blacktreatment ember-fillmotion crossfade-8fpower morphinstrument decay→three-symboliccurate rows
3s3
matches intent
NumberedList
template		teach14.9–22.2skinetic-buildicon·wireframe♪ —
We start by writing down the workflow as it really runs: every trigger, every step, every handoff between tools.
on-screen: Step 1: map the handoffs
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
4s4
first render · fix pending
ChecklistCard
templatedead_air		teach22.2–27.2skinetic-buildicon·white-knockout♪ —
Then we diagram it as tool calls.
on-screen: Each step = a tool call
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5s5
matches intent
TerminalRun
template		teach27.2–34.3skinetic-buildicon·liquid-chrome♪ —
We wire the apps as MCP servers, so the same assistant can touch your sheet, your storage, and your inbox through one
on-screen: Connect the tools via MCP
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual node-graphshape boxground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes
6s6
matches intent
CodeWindow
template		teach34.3–42.0skinetic-buildicon·ember-fill♪ —
It flows end to end: a trigger fires, the steps run in order, and the output lands where it belongs, no tabs
on-screen: Trigger -> steps -> output
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate codeLines, nodes, windowTitle
7s7
matches intent
JsonDiff
template		teach42.0–48.0skinetic-buildicon·wireframe♪ —
Where a step needs a decision, the model makes it in plain language instead of a brittle if-this-then-that node.
on-screen: Add the judgment calls
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate fileName, lines, nodes
8s8
matches intent
StackTrace
template		teach48.0–54.5skinetic-buildicon·white-knockout♪ —
We diagram the branches too: the happy path, the edge cases, and where a human still has to sign
on-screen: Branch when it matters
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual node-graphshape boxground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate errMsg, errType, fix, frames, nodes
9s9
matches intent
SchematicCard
template		teach54.5–61.7skinetic-buildicon·liquid-chrome♪ —
When a run fails, it logs why in readable language, so debugging is a conversation, not a hunt through node logs.
on-screen: Errors that explain themselves
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual node-graphshape boxground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes
10s10
matches intent
BlueprintGrid
template		teach61.7–67.9skinetic-buildicon·ember-fill♪ —
Every run flows to a log and a notification, so you know it happened and you have a receipt if it didn't.
on-screen: Run -> log -> notify
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, rows
11s11
matches intent
ProcessFlow
template		teach67.9–74.5skinetic-buildicon·wireframe♪ —
You trigger the same workflow two ways: on a schedule for the routine stuff, or just by asking when you need it
on-screen: Schedule it or speak it
expected on screen: black ground · a ProcessFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes, steps
12s12
matches intent
CheatSheet
template		teach74.5–80.3skinetic-buildicon·white-knockout♪ —
The shape is always the same: one assistant, a set of tools, and a workflow it follows.
on-screen: One assistant, many tools
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape boxground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes, points, uses
13s13
matches intent
StepFlow
template		teach80.3–86.3skinetic-buildicon·liquid-chrome♪ —
Because each step is just a tool call, swapping one app for another is a one-line change, not a
on-screen: Swap a tool, not a rebuild
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape boxground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, steps
14s14
matches intent
ListCard
template		teach86.3–93.1skinetic-buildicon·ember-fill♪ —
It all flows through the assistant: it picks the tool, runs the step, checks the result, and moves on.
on-screen: Tools -> assistant -> result
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate items, nodes
15s15
matches intent
FlowSchematic
template		teach93.1–99.5skinetic-buildicon·wireframe♪ —
Don't boil the ocean. Pick the one task everyone dreads and automate just that. Win, then expand.
on-screen: Start with one ugly task
expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes, stages
16s16
matches intent
LegacyCard
template		teach99.5–106.3skinetic-buildicon·white-knockout♪ —
We diagram the rollout: one flow proven, then the next, until a fleet of small automations runs your back
on-screen: From one flow to a fleet
expected on screen: black ground · a LegacyCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id LegacyCardvisual node-graphshape boxground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes
17s17
matches intent
RankList
template		proof106.3–112.7sreceipts-counticon·liquid-chrome♪ —
A team that ran on copy-paste gets hours back every week, with fewer mistakes than the humans were making.
on-screen: Hours back, every week
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate rows, statsLabels
18s18
matches intent
shared field
signature-3d		futurist112.7–118.9sspatial-parallaxicon·ember-fill♪ —
Soon the line blurs: you don't operate software, you tell it the outcome and it assembles the steps.
on-screen: Software that does the work
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape boxground blacktreatment ember-fillmotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
19s19
matches intent
shared field
signature-3d		resolve118.9–124.5scoalescenceicon·ember-fill♪ swell
Tell us the task you hate most and we'll automate it first. Start at temerarii.xyz.
on-screen: Automate your worst task
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→three-coalescence

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 12 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBlueskyEmailSMSBlog

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

tiktokMost of your work is not creative. It is the same handoffs over and over, and that part can run itself. (AI-assisted) Write the workflow down as it really runs: every trigger, every step, every handoff between tools. Diagram each step as a tool call. Wire the apps as MCP servers so one assistant can touch your sheet, your storage, and your inbox. A trigger fires, the steps run in order, the output lands where it belongs. Where a step needs judgment, the model decides in plain language. Pick the one task everyone dreads and automate just that.
instagramMost of your work isn't creative. It's the same handoffs, over and over. That part can run itself: Map every trigger and handoff Make each step a tool call Wire apps as MCP servers Let the model handle the judgment calls Start with the one task everyone dreads. #Automation #MCP #AItools #Workflow #Temerarii
linkedinMost of your work is not creative. It is the same handoffs over and over, and that part can run itself. Here is how, given away. The old way put a person between every app, copying from one tab into another all day, the human as duct tape. The method: 1. Write the workflow down as it really runs: every trigger, every step, every handoff between tools. 2. Diagram each step as a tool call. 3. Wire the apps as MCP servers, so one assistant can touch your sheet, your storage, and your inbox. 4. A trigger fires, the steps run in order, and the output lands where it belongs, no tabs. 5. Where a step needs a decision, the model makes it in plain language, not a brittle if-this-then-that node. 6. When a run fails, it logs why in readable language, so debugging is a conversation, not a hunt through logs. Because each step is just a tool call, swapping one app for another is a one-line change, not a rebuild. Don't boil the ocean. Pick the one task everyone dreads and automate just that. Tell us the task you hate most. temerarii.xyz
xMost of your work isn't creative. It's the same handoffs, over and over. Map every trigger and handoff Make each step a tool call Wire apps as MCP servers Model handles the judgment calls Start with the one task everyone dreads. temerarii.xyz
facebookMost of your work is not creative. It is the same handoffs over and over, and that part can run itself. Write the workflow down: every trigger, step, and handoff. Diagram each step as a tool call. Wire the apps as MCP servers so one assistant can touch your sheet, your storage, and your inbox. A trigger fires, the steps run in order, the output lands where it belongs. Where a step needs judgment, the model decides in plain language. Pick the one task everyone dreads and automate just that. temerarii.xyz
threadsMost of your work isn't creative. It's the same handoffs, over and over. That part can run itself. Map every trigger and handoff. Make each step a tool call. Wire the apps as MCP servers so one assistant touches your sheet, storage, and inbox. Let the model handle the judgment calls. Start with the one task everyone dreads.
pinterestHow to automate the boring 80% of your work: map every trigger and handoff, turn each step into a tool call, wire apps as MCP servers so one assistant runs them, and let the model handle the judgment calls. A plain workflow automation method that starts with the task everyone dreads.
blueskyMost of your work isn't creative. It's the same handoffs, over and over. Map every trigger and handoff. Make each step a tool call. Wire apps as MCP servers so one assistant touches your sheet, storage, and inbox. Model handles the judgment calls. Start with the task everyone dreads. temerarii.xyz
youtubeAutomate the Boring 80%: Map Your Handoffs Into Tool Calls With MCP Most of your work is not creative. It is the same handoffs over and over, and that part can run itself. This walks the full method and gives it away. The old way put a person between every app, copying from one tab into another all day, the human as duct tape. The method: 1. Write the workflow down as it really runs: every trigger, every step, every handoff between tools. 2. Diagram each step as a tool call. 3. Wire the apps as MCP servers, so one assistant can touch your sheet, your storage, and your inbox through one interface. 4. A trigger fires, the steps run in order, and the output lands where it belongs, no tabs. 5. Where a step needs a decision, the model makes it in plain language instead of a brittle if-this-then-that node. 6. When a run fails, it logs why in readable language, so debugging is a conversation. 7. Every run flows to a log and a notification, so you have a receipt if it did not. Because each step is just a tool call, swapping one app for another is a one-line change, not a rebuild. Don't boil the ocean: pick the one task everyone dreads and automate just that. Tell us the task you hate most and we will automate it first. temerarii.xyz

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

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