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-W45-Wedkind longformweek W45date 2026-11-11campaign longform-youtubepillar performancebeat asset videoduration 147.4sground 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-W45-Wed 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 · 147.4s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–17.3sspatial-parallaxicon·wireframe♪ bed_in
Posts pile up. Someone has to actually run the accounts. Today is social media management, the unglamorous part that keeps the engine turning. By the end you will know how to make a machine schedule, post, and track everything so you are not living in seven tabs.
on-screen: Run the accounts without the drudgery
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→Run the accounts without the drudgery
2s2
matches intent
NumberedList
template
teach17.3–35.3skinetic-buildicon·wireframe♪ node_lock
First move. Stop posting by hand on each platform. Wire one posting tool through MCP, we use Blotato, and connect all your accounts to it once. Now the agent posts everywhere from a single call. The setup takes an afternoon. It saves that afternoon back every single week after.
on-screen: One scheduler, every account
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→One scheduler, every accountcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach35.3–54.4skinetic-buildicon·wireframe♪ node_lock
Second move. The source file already lists what posts on which day. Have the agent read it and load the scheduler with the right dates automatically. You do not type dates. The machine knows Wednesday is a black-ground post because the plan said so, and it queues it for the right hour.
on-screen: Let the file set the dates
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→Let the file set the datescurate items, nodes
4s4
matches intent
BuildLog
template
teach54.4–74.2skinetic-buildicon·wireframe♪ node_lock
Third move. Trust nothing blindly. After scheduling, have the agent call the tool back and confirm each post went live. We pull the post status through the same MCP server. If one failed, the model flags it and retries. You find out from the machine, not from a customer asking where the post went.
on-screen: Check it posted, for real
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Check it posted, for realcurate lines, nodes
5s5
matches intent
JsonDiff
template
teach74.2–94.0skinetic-buildicon·wireframe♪ node_lock
Fourth move. Every post should leave a trail. Have the agent log each one into a single sheet or table, what went where and when. We write it to one record the model can read later. Next month, when you ask what worked, the answer is already written down, not lost in your memory.
on-screen: Keep one record of everything
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Keep one record of everythingcurate fileName, lines, nodes
6s6
matches intent
SchematicCard
template
teach94.0–111.3skinetic-buildicon·wireframe♪ node_lock
Fifth move. Before anything goes out, have the model scan the queue for holes. An empty day, a missing image, the same idea twice. It catches the boring mistakes that make a feed look sloppy. You approve a clean week instead of patching a broken one live.
on-screen: Fix the gaps before they post
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Fix the gaps before they postcurate nodes
7s7
matches intent
ListCard
template
proof111.3–129.0sreceipts-counticon·wireframe♪ node_lock
Honest proof. We do not babysit our own posting. The scheduler runs from the source file, confirms itself, and logs itself. The same management loop you just saw keeps The Big T-M live in public, with one person approving, not a room full of people copying and pasting.
on-screen: We manage ours hands-off
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We manage ours hands-offcurate items, statsLabels
8s8
matches intent
shared field
signature-3d
resolve129.0–147.4scoalescenceicon·wireframe♪ bed_out
That is social media management without the drudgery. One scheduler, dates from the file, confirmed posts, one record, a tidy queue. The dull work goes to the machine. Watch the whole thing run in public at office dot temerarii dot xyz, then wire your own accounts once and walk away.
on-screen: See the queue at the office
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→See the queue at the office

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)

youtubeSchedule, Post, and Confirm Your Whole Week With One Tool and the Source File Posts pile up and someone has to actually run the accounts. In this video we show how to make a machine schedule, post, and track everything so you are not living in seven tabs. The moves: - One scheduler, every account. Stop posting by hand on each platform. Wire one posting tool through MCP, we use Blotato, and connect all your accounts to it once. The agent posts everywhere from a single call. - Let the file set the dates. The source file already lists what posts on which day. Have the agent read it and load the scheduler with the right dates. You do not type dates. - Check it posted, for real. After scheduling, have the agent call the tool back and confirm each post went live. We pull the post status through the same MCP server. If one failed, the model flags it and retries. - Keep one record of everything. Have the agent log each post into a single sheet or table, what went where and when. Next month, when you ask what worked, the answer is already written down. - Fix the gaps before they post. Before anything goes out, have the model scan the queue for holes: an empty day, a missing image, the same idea twice. You approve a clean week instead of patching a broken one live. The honest proof: we do not babysit our own posting. The scheduler runs from the source file, confirms itself, and logs itself. One person approving, not a room full of people copying and pasting. The takeaway: one scheduler, dates from the file, confirmed posts, one record, a tidy queue. The dull work goes to the machine. Watch it run at office.temerarii.xyz. Keywords: social media management, scheduling, Blotato, MCP, posting automation.

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