Checklist the per-video bar — engine/sim
98.5/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W25-Sun-4 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 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 · 47.9s · 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 | The old way picked topics on a hunch and called it a content plan. on-screen: Strategy used to be a guess |
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→Strategy used to be a guess | |||||||
| 2 |  matches intent shared field signature-3d | hook | 5.5–10.7s | kinetic-build | icon·white-knockout | ♪ node_lock | Here is the move now: we mine the real questions people already ask. on-screen: Now we mine the questions people ask |
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 we mine the questions people ask | |||||||
| 3 |  matches intent NumberedList template | teach | 10.7–15.899999999999999s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Pull the questions from search, forums, and your own inbox into one list. on-screen: Pull search and forum questions |
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→Pull search and forum questionscurate items, nodes | |||||||
| 4 |  matches intent RankList template | proof | 15.9–21.1s | receipts-count | icon·white-knockout | ♪ node_lock | We cluster that list, then rank by how often each question shows up. on-screen: One list of real questions, ranked |
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→One list of real questions, rankedcurate rows, statsLabels | |||||||
| 5 |  matches intent CodeWindow template | diff | 21.1–26.1s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | A hunch makes content nobody wanted. Real questions make content people find. on-screen: Answer real questions, not your hunch |
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual codeshape octaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Answer real questions, not your hunchcurate codeLines, windowTitle | |||||||
| 6 |  matches intent ChecklistCard template | teach | 26.1–31.6s | kinetic-build | icon·white-knockout | ♪ node_lock | Then we turn each top question into one clear piece that answers it fully. on-screen: One question, one piece |
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→One question, one piececurate items, nodes | |||||||
| 7 |  matches intent StatScoreboard template | proof | 31.6–36.800000000000004s | receipts-count | icon·liquid-chrome | ♪ node_lock | The question becomes the title, so search and people both know it fits. on-screen: Top question becomes the title |
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→Top question becomes the titlecurate pillar, stats, statsLabels | |||||||
| 8 |  matches intent ProcessFlow template | step | 36.8–42.0s | kinetic-build | icon·white-knockout | ♪ node_lock | Mine questions, cluster them, rank by demand, then write the top ones first. on-screen: Mine, cluster, rank, then write |
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→Mine, cluster, rank, then writecurate stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 42.0–47.9s | coalescence | icon·liquid-chrome | ♪ bed_out | The Big T-M plans content by what people ask, not by what we feel like. on-screen: The Big T-M plans by demand |
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→The Big T-M plans by demand | |||||||
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)
tiktokHow to build a content plan that isn't a guess (AI-assisted): pull the real questions people ask from search and forums, cluster them, rank by demand, then write the top ones. The question becomes your title. #contentstrategy #marketing #seo
instagramStop guessing topics.
Mine the questions people actually ask.
Rank by demand. Answer the top ones.
#contentstrategy #contentmarketing #seo #marketing #creator
linkedinMost content plans are hunches. A better method: collect the real questions your audience asks from search, forums, and your inbox, cluster them, and rank by demand. The takeaway: let demand pick your topics, then make the question the title. You stop publishing things nobody searched for.
xYour content plan shouldn't be a hunch. Mine the questions people actually ask, rank by demand, write the top ones. Question becomes the title. temerarii.xyz
facebookWe stopped picking topics on a hunch. Now we mine the real questions people ask, cluster them, rank by demand, and answer the top ones first. Want the method? It's on the site.
threadsContent strategy in one line: stop guessing topics. Mine the questions people already ask, rank by how often they come up, and turn each into a piece. The question is the title.
pinterestContent strategy method: mine the real questions your audience asks, cluster and rank by demand, then write the top ones first. Make the question the title. Content marketing tips, content planning, SEO strategy.
blueskyBetter content plan: mine the real questions people ask, rank by demand, write the top ones. The question becomes your title. temerarii.xyz
youtubeBuild a Content Plan From Real Questions (Not Hunches)
Guessing topics gets you content nobody wanted. We show the method: pull the questions people actually ask from search, forums, and your inbox, cluster them, rank by demand, and write the top ones first. The question becomes your title, so search and readers both find it.