Checklist the per-video bar — engine/sim
86.6/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W34-Wed-3 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 · 50.2s · 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.0s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | Someone, somewhere, is copying the same data between tabs again right now. on-screen: The same task by hand, daily |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→The same task by hand, daily | |||||||
| 2 |  matches intent shared field signature-3d | hook | 5.0–10.5s | kinetic-build | icon·white-knockout | ♪ node_lock | Boring manual work feels free until you add up the hours it quietly eats. on-screen: Manual work hides the real cost |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Manual work hides the real cost | |||||||
| 3 |  matches intent NumberedList template | teach | 10.5–16.4s | kinetic-build | icon·liquid-chrome | ♪ node_lock | The method: write the trigger, the steps, and the result before you automate a thing. on-screen: Map the trigger, steps, result |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Map the trigger, steps, resultcurate items, nodes | |||||||
| 4 |  matches intent RankList template | proof | 16.4–21.9s | receipts-count | icon·white-knockout | ♪ node_lock | Mapping the flow first meant we automated it once instead of three broken times. on-screen: Mapped first, automated once |
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape tetraground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Mapped first, automated oncecurate rows, statsLabels | |||||||
| 5 |  matches intent CodeWindow template | diff | 21.9–27.4s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | Automate the boring parts and keep the human judgment where it earns its keep. on-screen: Automate boring, keep judgment |
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual codeshape tetraground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Automate boring, keep judgmentcurate codeLines, windowTitle | |||||||
| 6 |  matches intent ChecklistCard template | teach | 27.4–33.3s | kinetic-build | icon·white-knockout | ♪ node_lock | Now AI reads the map and wires the tools together with the logic in between. on-screen: AI connects the steps for you |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→AI connects the steps for youcurate items, nodes | |||||||
| 7 |  matches intent StatScoreboard template | proof | 33.3–38.8s | receipts-count | icon·liquid-chrome | ♪ node_lock | A chore that ate an hour each morning now runs before anyone wakes up. on-screen: A daily chore became invisible |
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→A daily chore became invisiblecurate pillar, stats, statsLabels | |||||||
| 8 |  matches intent FlowSchematic template | step | 38.8–44.3s | kinetic-build | icon·white-knockout | ♪ node_lock | Your step: write trigger, steps, result on one page before you touch any tool. on-screen: Write the flow before the code |
expected on screen: red ground · a FlowSchematic panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id FlowSchematicvisual pipelineshape tetraground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Write the flow before the codecurate stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 44.3–50.199999999999996s | coalescence | icon·liquid-chrome | ♪ bed_out | Soon you will describe the flow in a sentence and watch the wiring build itself. on-screen: Soon you describe it, it builds it |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Soon you describe it, it builds it | |||||||
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)
tiktokSomeone on your team is copying data between tabs RIGHT NOW. Boring work feels free until you add up the hours. The move: write the trigger, steps, and result on ONE page before automating. (AI-assisted) Then AI wires the tools together. Automate the boring, keep the judgment.
instagramThe same task, by hand, every day.
Manual work feels free. It isn't.
Map trigger to steps to result first.
AI wires the tools together.
#automation #workflow #productivity #aitools #temerarii
linkedinRight now, someone on your team is copying the same data between tabs again. Boring manual work feels free until you add up the hours it quietly eats. The method that fixes it: write the trigger, the steps, and the result before you automate anything, because mapping the flow first means you automate it once, not three broken times. What's new: AI reads the map and wires the tools together with the logic in between, turning a one-hour morning chore into something that runs before anyone wakes up. Takeaway: automate the boring, keep the human judgment.
xSomeone on your team is copying data between tabs right now. Map the trigger, steps, result on one page first. Then AI wires the tools together. Automate the boring, keep the judgment. temerarii.xyz
facebookRight now, someone on your team is copying the same data between tabs again. Boring manual work feels free until you add up the hours it eats. The move: write the trigger, steps, and result on one page before you automate anything. Then AI wires the tools together, and a one-hour morning chore runs before anyone wakes up. Automate the boring, keep the judgment. Got a chore worth killing? Tell us.
threadsSomeone on your team is copying data between tabs right now.
Boring work feels free until you add up the hours.
Write the trigger, steps, result on one page first. Then AI wires the tools. Automate the boring, keep the judgment.
pinterestWorkflow automation that actually sticks: write the trigger, the steps, and the result on one page before you automate anything. Map it once so you build it once. Then use AI to wire your tools together. Workflow automation, productivity systems, business automation, AI tools.
blueskySomeone on your team is copying data between tabs right now. Map the trigger, steps, result first. Then AI wires the tools. Automate the boring, keep the judgment. temerarii.xyz
youtubeAutomated Workflows: Map It Before You Automate It
Right now, someone on your team is copying the same data between tabs again. Boring manual work feels free until you add up the hours it quietly eats. The method that fixes it: write the trigger, the steps, and the result before you automate anything, because mapping the flow first means you automate it once instead of three broken times. What's new: AI reads the map and wires the tools together with the logic in between, turning a one-hour morning chore into something that runs before anyone wakes up. Soon you'll describe the flow in a sentence and watch the wiring build itself.
Your step: write trigger, steps, result on one page before you touch any tool. Automate the boring, keep the judgment.
AI-assisted production. More at temerarii.xyz