Checklist the per-video bar — engine/sim
75.9/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-ask-the-operator-W41-Tue good|bad)⚠ 7 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 5 scenes · 25.0s · 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 | hook | 0–5.0s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Question: I built an automation, but how do I make it just run on its own? on-screen: "Schedule the automation?" |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→"Schedule the automation?" | |||||||
| 2 |  first render · fix pending NumberedList templatedead_air | teach | 5.0–10.0s | kinetic-build | icon·white-knockout | ♪ node_lock | We used to babysit scripts by hand. Now a cron schedule sets when it runs and a saved prompt sets what it does. on-screen: Cron plus a prompt |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape knotground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Cron plus a promptcurate items, nodes | |||||||
| 3 |  matches intent ComparisonTable template | proof | 10.0–15.0s | receipts-count | icon·liquid-chrome | ♪ node_lock | Take one working automation and give it a weekly trigger so you stop running it. on-screen: Set one schedule |
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape knotground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Set one schedulecurate colA, colB, rows, statsLabels | |||||||
| 4 |  first render · fix pending AnnotatedDiagram templatedead_airgeneric_scene | step | 15.0–20.0s | kinetic-build | icon·white-knockout | ♪ node_lock | Ask the Operator |
expected on screen: red ground · a AnnotatedDiagram panel over a dimmed Signal Field · Magister leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id AnnotatedDiagramvisual pipelineshape knotground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Ask the Operatorcurate callouts, stages, steps | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 20.0–25.0s | coalescence | icon·white-knockout | ♪ bed_out | Ask the Operator |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Ask the Operator | |||||||
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 9 destinations
LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky
Social captions supplemental published copy · per channel (comp_id level)
tiktokAsk the operator: I built an automation, how do I make it just run on its own? Pair a cron schedule with a saved prompt. Take one working automation and give it a weekly trigger. (AI-assisted)
instagram"How do I make my automation just run?"
Cron plus a saved prompt.
We used to babysit scripts by hand.
Give one working automation a weekly trigger.
#automation #cron #aiagents #asktheoperator #temerarii
linkedinAsk the operator: I built an automation, but how do I make it just run on its own?
We used to babysit scripts, kicking each one off by hand and watching it finish. The answer is a cron schedule paired with a saved prompt: cron decides when, the prompt decides what.
Start small. Take one automation that already works and give it a weekly trigger so you stop running it manually. Once that runs untouched for a few weeks, add the next one.
xAsk the operator: how do I make my automation just run? Cron plus a saved prompt. Take one working automation, give it a weekly trigger. temerarii.xyz
facebookThis week's question: I built an automation, but how do I make it just run on its own? The answer is a cron schedule paired with a saved prompt. We used to babysit scripts by hand. Start with one automation that already works and give it a weekly trigger so you stop running it. More at temerarii.xyz.
threadsAsk the operator: I built an automation, how do I make it just run on its own?
Cron plus a saved prompt. We used to babysit scripts by hand. Take one working automation and give it a weekly trigger so you stop running it.
pinterestHow to make an automation run on its own: pair a cron schedule with a saved prompt so the schedule handles when and the prompt handles what. Start by giving one working automation a weekly trigger instead of running it by hand.
blueskyAsk the operator: how do I make my automation just run? Cron plus a saved prompt. Take one working automation, give it a weekly trigger.
youtubeTitle: Ask the Operator: Make Your Automation Run On Its Own With Cron
The question: I built an automation, but how do I make it just run on its own? The answer is a cron schedule paired with a saved prompt, where cron decides when and the prompt decides what. We used to babysit scripts by hand. Start by taking one automation that already works and giving it a weekly trigger so you stop running it.