Checklist the per-video bar — engine/sim
86.6/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W32-Fri-1 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 · 56.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.5s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | Making content used to be one tired person doing every step alone, all night. on-screen: Content used to be one person, all |
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Content used to be one person, all night | |||||||
| 2 |  matches intent shared field signature-3d | hook | 5.5–12.1s | kinetic-build | icon·white-knockout | ♪ node_lock | Now it is a pipeline, where each step hands clean work to the next without a human. on-screen: Now it's a pipeline, not a person |
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape octaground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Now it's a pipeline, not a person | |||||||
| 3 |  matches intent NumberedList template | teach | 12.1–18.4s | kinetic-build | icon·liquid-chrome | ♪ node_lock | The move is breaking the job into stages: script, voice, render, caption, each its own step. on-screen: Break the job into small stages |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape octaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Break the job into small stagescurate items, nodes | |||||||
| 4 |  matches intent RankList template | proof | 18.4–25.0s | receipts-count | icon·white-knockout | ♪ node_lock | Each stage outputs one tidy file the next stage reads, so nothing gets lost in a chat. on-screen: Each stage outputs a file |
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape octaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Each stage outputs a filecurate rows, statsLabels | |||||||
| 5 |  matches intent BuildLog template | diff | 25.0–30.2s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | One giant do-everything prompt always breaks; small stages fail loud and fix fast. on-screen: One giant prompt always breaks |
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape octaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→One giant prompt always breakscurate codeLines, lines | |||||||
| 6 |  matches intent ChecklistCard template | teach | 30.2–37.5s | kinetic-build | icon·white-knockout | ♪ node_lock | Let AI fill each stage on its own, so a bad output ruins one step, not the whole run. on-screen: Let AI fill each stage, not all |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Let AI fill each stage, not allcurate items, nodes | |||||||
| 7 |  matches intent StatScoreboard template | proof | 37.5–43.8s | receipts-count | icon·liquid-chrome | ♪ node_lock | When a video looks wrong, you fix the one stage that broke, not the entire machine. on-screen: Isolated stages are easy to debug |
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape octaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Isolated stages are easy to debugcurate pillar, stats, statsLabels | |||||||
| 8 |  matches intent ProcessFlow template | step | 43.8–50.099999999999994s | kinetic-build | icon·white-knockout | ♪ node_lock | Stage the work, save each file, chain the steps, and the engine runs while you sleep. on-screen: Stage it, file it, chain it |
expected on screen: red ground · a ProcessFlow panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ProcessFlowvisual pipelineshape octaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Stage it, file it, chain itcurate stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 50.1–56.0s | coalescence | icon·liquid-chrome | ♪ bed_out | That is a creative workflow that runs like an engine instead of running you ragged. on-screen: A content engine, not a slog |
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→A content engine, not a slog | |||||||
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)
tiktokOur AI content engine, explained (AI-assisted). Stop doing every step alone at midnight. Break the job into STAGES — script, voice, render, caption — and each stage outputs one tidy file the next one reads. One giant do-everything prompt always breaks; small stages fail loud and fix fast. When a video looks wrong, you fix the ONE stage that broke, not the whole machine. #aicontent #workflow #buildinpublic
instagramContent as a pipeline, not a person.
Stages: script, voice, render, caption.
Each stage outputs one file.
Fix the broken stage, not the machine.
#aicontent #workflow #automation #buildinpublic #creator
linkedinHow we turned content creation into an engine:
The old way was one tired person doing every step alone. The fix is a pipeline — each step hands clean work to the next.
The principle: break the job into stages (script, voice, render, caption) where each stage outputs one tidy file the next stage reads. Nothing gets lost in a chat thread. A single do-everything prompt always breaks; small stages fail loud and are fast to fix.
Let AI fill each stage independently, so a bad output ruins one step, not the whole run. When a video looks wrong, you fix the one stage that broke — not the entire machine.
Takeaway: stage it, file it, chain it.
xOur AI content engine: break the job into stages (script, voice, render, caption), each outputting one file the next step reads. A giant do-everything prompt always breaks; small stages fail loud and fix fast. temerarii.com
facebookMaking content used to be one tired person doing every step alone at midnight. Now it's a pipeline. Break the job into stages — script, voice, render, caption — and each stage outputs one tidy file the next one reads. A single do-everything prompt always breaks; small stages fail loud and fix fast. When a video looks wrong, you fix the one stage that broke, not the whole machine. Here's the build.
threadsOur AI content engine: break the job into stages — script, voice, render, caption — and each stage outputs one tidy file the next reads. A giant do-everything prompt always breaks; small stages fail loud and fix fast. Fix the broken stage, not the whole machine.
pinterestHow to build an AI content engine: break content creation into pipeline stages — script, voice, render, caption — where each step outputs a file the next reads. A guide to modular, debuggable creative workflows that beat one giant prompt. AI content automation explained.
blueskyOur AI content engine: break the job into stages (script, voice, render, caption), each outputting one file the next reads. A giant do-everything prompt always breaks; small stages fail loud and fix fast. temerarii.com
youtubeCreative Workflows: Build an AI Content Engine, Not a Slog
Making content used to be one tired person doing every step alone at midnight. This short shows how to turn it into a pipeline: break the job into stages — script, voice, render, caption — where each stage outputs one tidy file the next stage reads, so nothing gets lost in a chat thread. A single do-everything prompt always breaks; small stages fail loud and are fast to fix. When a video looks wrong, you fix the one stage that broke, not the entire machine.
More at temerarii.com.