Checklist the per-video bar — engine/sim
86.6/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W29-Thu-2 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 · 69.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–7.7s | spatial-parallax | icon·wireframe | ♪ bed_in | Most teams do the same boring task by hand every day and call the wasted hour part of the job. on-screen: The same task, every single day |
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→The same task, every single day | |||||||
| 2 |  matches intent shared field signature-3d | hook | 7.7–15.8s | kinetic-build | icon·ember-fill | ♪ node_lock | Here is the truth: if you can describe a task in clear steps, you can hand those steps to a machine. on-screen: If you can describe it, you can |
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground blacktreatment ember-fillmotion kinetic-buildpower laser-lockinstrument laser-trace→If you can describe it, you can script it | |||||||
| 3 |  matches intent NumberedList template | teach | 15.8–22.8s | kinetic-build | icon·wireframe | ♪ node_lock | We write the steps out in plain words first, because a workflow you cannot explain cannot be automated. on-screen: Write the steps down first |
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write the steps down firstcurate items, nodes | |||||||
| 4 |  matches intent RankList template | proof | 22.8–30.9s | receipts-count | icon·white-knockout | ♪ node_lock | Then we connect the tools with a small script that takes the output of one and feeds it to the next. on-screen: Connect the tools with code |
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Connect the tools with codecurate rows, statsLabels | |||||||
| 5 |  matches intent BuildLog template | diff | 30.9–38.199999999999996s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | The Big T-M does not automate the thinking. We automate the boring parts and keep the judgment for people. on-screen: We automate the boring, keep the judgment |
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape boxground blacktreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→We automate the boring, keep the judgmentcurate codeLines, lines | |||||||
| 6 |  matches intent ChecklistCard template | teach | 38.2–45.5s | kinetic-build | icon·ember-fill | ♪ node_lock | Put one human checkpoint in the middle, so a person approves the risky step before the machine commits it. on-screen: Add a checkpoint a human approves |
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Add a checkpoint a human approvescurate items, nodes | |||||||
| 7 |  matches intent StatScoreboard template | proof | 45.5–53.9s | receipts-count | icon·wireframe | ♪ node_lock | What was an hour of clicking becomes one button you press, and the freed hour goes to work that needs a brain. on-screen: An hour a day becomes a button |
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→An hour a day becomes a buttoncurate pillar, stats, statsLabels | |||||||
| 8 |  matches intent FlowSchematic template | step | 53.9–60.9s | kinetic-build | icon·white-knockout | ♪ node_lock | Try it: write your steps, script the most boring one, and add a human checkpoint before anything irreversible. on-screen: Do this |
expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id FlowSchematicvisual pipelineshape boxground blacktreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Do this: write steps, script one, add a gatecurate stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 60.9–69.0s | coalescence | icon·wireframe | ♪ bed_out | Good automation is not about doing more. It is about getting your hours back for the work only you can do. on-screen: Automation gives time back |
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Automation gives time back | |||||||
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)
tiktokIf you can describe a task in clear steps, you can hand it to a machine (AI-assisted method). Write the steps in plain words first, connect the tools with a small script, then add ONE human checkpoint before the risky step. Automate the boring, keep the judgment. #automation #workflow #productivity
instagramIf you can describe it, you can script it.
Write the steps in plain words.
Connect the tools with code.
Add a human checkpoint before the risky part.
Automate the boring, keep the judgment.
#automation #workflow #productivity #nocode #tech
linkedinAutomated workflows, the honest version. Most teams do the same boring task by hand every day and call the wasted hour part of the job. But if you can describe a task in clear steps, you can hand those steps to a machine. Write the steps in plain words first (a workflow you can't explain can't be automated), connect the tools with a small script that feeds one output into the next, and add one human checkpoint so a person approves the risky step before the machine commits it. Automate the boring; keep the judgment.
xIf you can describe a task in clear steps, you can script it. Write the steps in plain words, connect the tools with a small script, add ONE human checkpoint before the risky step. Automate the boring, keep the judgment.
facebookMost teams do the same boring task by hand every day and call the wasted hour part of the job. But if you can describe a task in clear steps, you can hand those steps to a machine. Write the steps in plain words first, connect the tools with a small script, and add one human checkpoint before anything irreversible. Automate the boring, keep the judgment. Full method in the video.
threadsIf you can describe a task in clear steps, you can script it. Write the steps in plain words first, connect the tools with a small script, add ONE human checkpoint before the risky step. Automate the boring, keep the judgment.
pinterestWorkflow automation guide: automate repetitive tasks, write the steps first, connect tools with scripts, human in the loop checkpoint, save time, no-code automation, business process. How an hour of clicking becomes one button you press.
blueskyIf you can describe a task in clear steps, you can script it. Write the steps in plain words, connect the tools with a small script, add ONE human checkpoint before the risky step. Automate the boring, keep the judgment.
youtubeAutomated Workflows: If You Can Describe It, You Can Script It
Most teams do the same boring task by hand every day and call the wasted hour part of the job. But if you can describe a task in clear steps, you can hand those steps to a machine. Write the steps in plain words first (a workflow you can't explain can't be automated), connect the tools with a small script that feeds one output into the next, and add one human checkpoint so a person approves the risky step before the machine commits it. Automate the boring; keep the judgment. AI-assisted, human-judged.