Checklist the per-video bar — engine/sim
100.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review longform-W27-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
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 7 scenes · 149.5s · 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–20.9s | spatial-parallax | icon·3d-extrude | ♪ bed_in | The hub is coming, and a lot of what makes it run is invisible. It is the jobs that happen the same way every single time, with no human pressing go. Today is only about automated workflows. You will learn how to take one repeat task off your plate for good, the exact way we do it. on-screen: Automated workflows, step by step |
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·3d-extrude logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground whitetreatment 3d-extrudemotion spatial-parallaxpower summoninstrument summon→Automated workflows, step by step | |||||||
| 2 |  matches intent NumberedList template | teach | 20.9–41.8s | kinetic-build | icon·wireframe | ♪ node_lock | First move, and it feels too simple. Before any code, write the job down as a list of steps a child could follow. Open this, copy that, paste here, send. If you cannot list the steps, you cannot automate them. Most failed automations skipped this. They tried to teach a machine a job nobody had spelled out. on-screen: Write down every step first |
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write down every step firstcurate items, nodes | |||||||
| 3 |  matches intent ChecklistCard template | teach | 41.8–64.8s | kinetic-build | icon·wireframe | ♪ node_lock | Second move. Take each step and find the tool that already does it. Posting goes to a posting tool, logging goes to a sheet, sending goes to email. You connect the agent to each tool through an MCP server, which is a small adapter that lets one brain press all those buttons. Now your list of steps has a worker behind every line. on-screen: Hand each step to a tool |
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Hand each step to a toolcurate items, nodes | |||||||
| 4 |  matches intent LogStream template | teach | 64.8–86.8s | kinetic-build | icon·wireframe | ♪ node_lock | Third move. Never point a new workflow at real customers on day one. Run it on a fake job. A test post, a test email to yourself, a test row. Watch every step land. When the fake job goes clean from start to finish, then you let real work through. This is the difference between an automation and an accident. on-screen: Run it on a fake job first |
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id LogStreamvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Run it on a fake job firstcurate nodes, rows | |||||||
| 5 |  matches intent ProcessFlow template | teach | 86.8–110.19999999999999s | kinetic-build | icon·wireframe | ♪ node_lock | The proof is dull on purpose. The posts for this very campaign go out through a workflow exactly like that. Named steps, a tool behind each one, tested on fakes before it ever touched a real account. Nobody copies and pastes them by hand. That is hours a week that quietly disappeared, and we did not invent a number to impress you about it. on-screen: Our posting runs untouched |
expected on screen: white ground · a ProcessFlow panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ProcessFlowvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Our posting runs untouchedcurate nodes, steps | |||||||
| 6 |  matches intent RankList template | proof | 110.2–129.3s | receipts-count | icon·wireframe | ♪ node_lock | So that is an automated workflow. Steps written plain, a tool per step, tested on a fake before it goes live. Your step is to pick the one task you do every week that bores you most. Write its steps down today. That list is the whole job. See more at office.temerarii.xyz. on-screen: Pick one repeat job |
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape knotground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Pick one repeat jobcurate rows, statsLabels | |||||||
| 7 |  matches intent shared field signature-3d | resolve | 129.3–149.5s | coalescence | icon·3d-extrude | ♪ bed_out | One last thing. Good automation is supposed to be boring. No drama, no surprises, just the same job done right while you do something that needs a human. If your workflow is exciting, something is broken. Aim for the quiet kind. The hub is full of quiet jobs, and that is exactly why it holds. on-screen: Boring is the point |
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→Boring is the point | |||||||
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)
youtubeHow to Automate a Repeat Task: Write the Steps, Wire the Tools, Test on a Fake
A lot of what runs a business is invisible, the jobs that happen the same way every time with no human pressing go. This walkthrough shows how to take one repeat task off your plate for good, the exact way we do it. The skill is naming the steps, not the typing.
The method:
- Write down every step first, like a recipe a child could follow. Open this, copy that, paste here, send. If you cannot list the steps, you cannot automate them. Most failed automations skipped this.
- Hand each step to a tool that already does it. Posting goes to a posting tool, logging goes to a sheet, sending goes to email. You connect the agent to each tool through an MCP server, a small adapter that lets one brain press all the buttons.
- Run it on a fake job first. A test post, a test email to yourself, a test row. Watch every step land. When the fake job goes clean start to finish, then you let real work through. That is the difference between an automation and an accident.
Good automation is supposed to be boring. No drama, no surprises, just the same job done right while you do something that needs a human. If your workflow is exciting, something is broken.
Your step: pick the one task you do every week that bores you most and write its steps down today. That list is the whole job. See more at office.temerarii.xyz.
Keywords: workflow automation, MCP server, business automation, no-code steps, task automation, small business operations.