Checklist the per-video bar — engine/sim
97.8/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-ask-the-operator-W23-Tue good|bad)⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarerendered16:9 Widerendered9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 3/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 5 scenes · 33.7s · 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–6.4s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Straight from the inbox: my site is small, so which keywords do I even chase first? on-screen: Small site. Which keywords? |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→Small site. Which keywords? | |||||||
| 2 |  matches intent NumberedList template | teach | 6.4–12.5s | kinetic-build | icon·white-knockout | ♪ node_lock | The operator's answer: skip the big terms, the budgets there will bury you. on-screen: Skip the big terms |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Skip the big termscurate items, nodes | |||||||
| 3 |  matches intent RankList template | proof | 12.5–22.6s | receipts-count | icon·liquid-chrome | ♪ node_lock | Open Search Console, sort queries by position, and find the ones sitting at eleven through twenty. One rewrite moves them. on-screen: Positions 11 to 20 are gold |
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Positions 11 to 20 are goldcurate rows, statsLabels | |||||||
| 4 |  matches intent FlowSchematic template | step | 22.6–27.6s | kinetic-build | icon·white-knockout | ♪ node_lock | Pick a single page-two query this week and rewrite that page around it. on-screen: One query. One rewrite. |
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→One query. One rewrite.curate stages, steps | |||||||
| 5 |  matches intent shared field signature-3d | resolve | 27.6–33.7s | coalescence | icon·white-knockout | ♪ bed_out | Got a question for the operator? Send it in. Plain answers only, always. on-screen: Send your question |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Send your question | |||||||
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)
tiktokInbox question: which keywords should a small site chase? Skip the giant terms. Pull your page-two queries and pick one. (AI-assisted)
instagramAsk the Operator: which keywords should a small site go after? Not the huge ones. Open Search Console, find your page-two queries, pick one, and write the better page. #SEO
linkedinA founder asked which keywords a small site should chase. Honest answer: not the big-volume terms, you will lose to everyone. Pull your page-two queries in Search Console, pick the one closest to a sale, and write the best page on the internet for it.
xQ: which keywords should a small site chase? Not the big ones. Pull your page-two queries in Search Console, pick one near a sale, write the best page for it.
facebookSomeone asked which keywords a small site should target. Skip the giant terms. Pull your own page-two queries in Search Console and pick the one closest to a sale.
threadsWhich keywords should a small site chase? Not the big ones you will lose. Pull your page-two queries in Search Console and pick one near a sale.
pinterestSmall-site SEO keyword strategy: ignore high-volume terms, pull page-two queries in Google Search Console, target the one closest to a sale.
blueskyWhich keywords should a small site chase? Not the big ones. Pull your page-two Search Console queries, pick one near a sale, write the best page for it.
youtubeAsk the Operator: which keywords should a small site chase? Do not fight for the giant terms. Open Search Console, find the queries where you are stuck on page two, pick the one closest to a sale, and make the best page for it.