Checklist the per-video bar — engine/sim
86.6/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W32-Sat-4 good|bad)⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_sequence_across_assetsdup_set_across_assets · see docs/strategy/VIDEO-CHECKLIST.md
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 9 scenes · 53.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 | open | 0–5.9s | spatial-parallax | icon·ember-fill | ♪ bed_in | For years the boring steps got done by hand, late, by whoever forgot to leave. on-screen: We used to do the boring steps |
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→We used to do the boring steps by hand | |||||||
| 2 |  matches intent shared field signature-3d | hook | 5.9–11.4s | kinetic-build | icon·color | ♪ node_lock | Now an automated workflow does the dull, repeatable parts while people do the thinking. on-screen: Now a workflow does the dull parts |
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Now a workflow does the dull parts | |||||||
| 3 |  matches intent NumberedList template | teach | 11.4–17.3s | kinetic-build | icon·color | ♪ node_lock | The move is writing the steps out in plain words first, before you automate anything. on-screen: Write the steps before you automate |
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Write the steps before you automatecurate items, nodes | |||||||
| 4 |  matches intent ComparisonTable template | proof | 17.3–23.200000000000003s | receipts-count | icon·color | ♪ node_lock | If you cannot write the steps clearly, you cannot automate them, only hide the mess. on-screen: You can't automate a fuzzy process |
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape tetraground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→You can't automate a fuzzy processcurate colA, colB, rows, statsLabels | |||||||
| 5 |  matches intent BuildLog template | diff | 23.2–29.1s | crossfade-8f | icon·color | ♪ node_lock | Automating a messy process does not fix it; it just makes the chaos happen faster. on-screen: Automating chaos just speeds the chaos |
expected on screen: white ground · a BuildLog panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape tetraground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Automating chaos just speeds the chaoscurate codeLines, lines | |||||||
| 6 |  matches intent ChecklistCard template | teach | 29.1–35.4s | kinetic-build | icon·color | ♪ node_lock | Then connect your tools with a simple trigger: when this happens, do that next, no clicks. on-screen: Connect tools with a trigger |
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Connect tools with a triggercurate items, nodes | |||||||
| 7 |  matches intent KpiGrid template | proof | 35.4–40.9s | receipts-count | icon·color | ♪ node_lock | Each trigger quietly deletes one more copy-paste tax you have been paying for years. on-screen: Triggers replace the copy-paste tax |
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape tetraground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Triggers replace the copy-paste taxcurate kpis, statsLabels | |||||||
| 8 |  matches intent PipelineMap template | step | 40.9–47.5s | kinetic-build | icon·color | ♪ node_lock | Map the steps, wire the triggers, watch it for a week, then trust it to run alone. on-screen: Map it, trigger it, watch it |
expected on screen: white ground · a PipelineMap panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id PipelineMapvisual pipelineshape tetraground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Map it, trigger it, watch itcurate stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 47.5–53.0s | coalescence | icon·ember-fill | ♪ bed_out | Automated workflows hand the dull work to machines so the thinking stays with you. on-screen: Automate the dull, keep the thinking |
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Automate the dull, keep the thinking | |||||||
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)
tiktokAutomate your busywork the right way. The move people skip: write the steps out in PLAIN WORDS first. If you can't write the process clearly, you can't automate it — you'll just hide the mess. Automating chaos only makes the chaos happen faster. Then connect tools with simple triggers: when THIS happens, do THAT, no clicks. #automation #workflow #productivity
instagramAutomate the dull, keep the thinking.
Write the steps in plain words first.
Can't write it? Can't automate it.
Connect tools with simple triggers.
#automation #workflow #productivity #nocode #buildinpublic
linkedinBefore you automate anything, write the steps down. Here's why:
The instinct is to automate the boring work first. But automating a messy process doesn't fix it — it just makes the chaos happen faster.
So the real first move is to write the steps out in plain words. If you can't write the process clearly, you can't automate it; you can only hide the mess. Once the steps are clear, connect your tools with simple triggers: when this happens, do that next, no clicks. Each trigger deletes one more copy-paste tax you've been paying for years.
Takeaway: map it, trigger it, watch it for a week, then trust it to run alone.
xAutomate busywork the right way: write the steps in plain words FIRST. Can't write the process clearly? You can't automate it — you'll just speed up the chaos. Then connect tools with simple triggers. temerarii.com
facebookFor years the boring steps got done by hand, late, by whoever forgot to leave. Automated workflows fix that — but only if you do it right. Write the steps out in plain words first. If you can't write the process clearly, you can't automate it; you'll just hide the mess. Automating chaos only makes the chaos happen faster. Then connect your tools with simple triggers. Here's how to start.
threadsAutomate busywork the right way: write the steps in plain words FIRST. If you can't write the process clearly, you can't automate it — you'll just hide the mess. Automating chaos only speeds up the chaos. Then connect tools with simple triggers: when this happens, do that.
pinterestAutomated workflows explained: how to automate business busywork the right way. Why you must write your process in plain steps first, how automating chaos backfires, and how to connect tools with simple triggers. A no-code automation and productivity guide for beginners.
blueskyAutomate busywork the right way: write the steps in plain words FIRST. Can't write the process clearly? You can't automate it — you'll just speed up the chaos. Then connect tools with simple triggers. temerarii.com
youtubeAutomated Workflows: Write the Steps Before You Automate
For years the boring steps got done by hand, late, by whoever forgot to leave. Automated workflows fix that — but only if you do it right. This short covers the step people skip: write the process out in plain words first. If you can't write it clearly, you can't automate it; you'll just hide the mess, because automating chaos only makes the chaos happen faster. Once the steps are clear, connect your tools with simple triggers: when this happens, do that next.
More at temerarii.com.