Checklist the per-video bar — engine/sim
100.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review longform-W36-Mon 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
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 6 scenes · 148.3s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  matches intent shared field signature-3d | open | 0–24.8s | spatial-parallax | icon·white-knockout | ♪ bed_in | The week is about content strategy that moves the needle, but a strategy that never gets posted is a diary. So today is about the unglamorous part: social media management, the actual scheduling and shipping. You will learn how to run a week of posts without a human babysitting a clock. The work is real, but a machine can hold the clock so you do not have to. on-screen: The boring part nobody schedules |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→The boring part nobody schedules | |||||||
| 2 |  matches intent NumberedList template | teach | 24.8–53.6s | kinetic-build | icon·white-knockout | ♪ node_lock | Step one. Stop keeping your posts in your head and stop keeping them in a dozen apps. Keep them in one file: a simple list where each post has a date, a platform, the text, and the file name of its image or video. We keep ours as plain data the agent can read and write. When the post is data, a tool can ship it. When it lives in your memory, only you can, and you will forget. on-screen: Keep posts as plain data |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Keep posts as plain datacurate items, nodes | |||||||
| 3 |  matches intent ChecklistCard template | teach | 53.6–77.4s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Step two. Connect the accounts through one door. We use an MCP server, which is just a small adapter that lets one agent talk to many platforms with the same commands. The model says post this here at this time, and the adapter handles the messy login details for each network. You stop logging into seven sites. You give one instruction and it fans out. on-screen: One agent talks to every account |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→One agent talks to every accountcurate items, nodes | |||||||
| 4 |  matches intent BuildLog template | teach | 77.4–100.10000000000001s | kinetic-build | icon·white-knockout | ♪ node_lock | Step three. Hand the clock to a schedule. We set a simple recurring job on the computer that wakes the agent each morning, reads the file, finds today's posts, and ships them. No app, no paid scheduler, just a timer and the file. The strategy decides what; the timer decides when; you decide nothing at nine a.m., which is the entire point. on-screen: Let a timer press post |
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Let a timer press postcurate lines, nodes | |||||||
| 5 |  matches intent ListCard template | proof | 100.1–123.1s | receipts-count | icon·liquid-chrome | ♪ node_lock | The honest proof: the posts you see from us go out on a timer, not because someone remembered. We built it, watched it ship a week, and caught the one post that went out with a broken image. That is the real test of management. Not that it works once, but that you find the one thing that broke before your audience does. on-screen: It runs while we are asleep |
expected on screen: red ground · a ListCard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ListCardvisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→It runs while we are asleepcurate items, statsLabels | |||||||
| 6 |  matches intent shared field signature-3d | resolve | 123.1–148.29999999999998s | coalescence | icon·white-knockout | ♪ bed_out | So the takeaway: management is just data plus one door plus a timer. Write your posts as a list, connect the accounts through a single adapter, and let a schedule press the button. You keep the judgment; the machine keeps the calendar. Your next step: watch a real week ship itself at office dot temerarii dot xyz, then build your own small list and let a timer carry it. on-screen: Watch the schedule run live |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Watch the schedule run live | |||||||
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 a week of social posts with no human babysitting the clock
A content plan that never gets posted is a diary. This is the unglamorous part: the actual scheduling and shipping, run by a machine so you do not have to hold the clock.
The method:
- Keep your posts as plain data. One file where each post has a date, a platform, the text, and the file name of its image or video. When a post is data, a tool can ship it. When it lives in your head, only you can, and you will forget.
- Connect every account through one door. We use an MCP server, a small adapter that lets one agent talk to many platforms with the same commands. You stop logging into seven sites and give one instruction that fans out.
- Let a timer press post. A simple recurring job wakes the agent each morning, reads the file, finds today's posts, and ships them. No app, no paid scheduler, just a timer and the file.
The honest proof: our posts go out on a timer, not because someone remembered. We built it, watched it ship a week, and caught the one post that went out with a broken image. That is the real test of management, finding the broken thing before your audience does.
Watch a real week ship itself at office.temerarii.xyz, then build your own small list and let a timer carry it.
Keywords: social media scheduling automation, MCP posting, cron job, content calendar as data.