Checklist the per-video bar — engine/sim
86.6/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W30-Mon-4 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 · 57.8s · 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–6.3s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | SEO used to be stuffing a page with keywords and hoping a robot rewarded the clutter. on-screen: SEO used to be keyword stuffing |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→SEO used to be keyword stuffing | |||||||
| 2 |  matches intent shared field signature-3d | hook | 6.3–11.8s | kinetic-build | icon·white-knockout | ♪ node_lock | Now answer engines read for meaning, and they quote the page that actually helps. on-screen: Now answer engines read for meaning |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Now answer engines read for meaning | |||||||
| 3 |  matches intent NumberedList template | teach | 11.8–18.8s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Write the clearest answer to one real question, then mark it up with schema so machines parse it. on-screen: Write the answer, then add the schema |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Write the answer, then add the schemacurate items, nodes | |||||||
| 4 |  matches intent RankList template | proof | 18.8–25.8s | receipts-count | icon·white-knockout | ♪ node_lock | Clean schema and a TL;DR get your page quoted in AI answers, not just listed on page two. on-screen: Schema gets you quoted, not just ranked |
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape dodecaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Schema gets you quoted, not just rankedcurate rows, statsLabels | |||||||
| 5 |  matches intent JsonDiff template | diff | 25.8–32.4s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | Most chase the algorithm. We write for the human first, then make it easy for the parser. on-screen: We write for the person, then the |
expected on screen: red ground · a JsonDiff panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id JsonDiffvisual codeshape dodecaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→We write for the person, then the parsercurate codeLines, fileName, lines | |||||||
| 6 |  matches intent ChecklistCard template | teach | 32.4–39.4s | kinetic-build | icon·white-knockout | ♪ node_lock | Add FAQ schema so each real question becomes a block an engine can lift straight into an answer. on-screen: Add FAQ schema to capture questions |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Add FAQ schema to capture questionscurate items, nodes | |||||||
| 7 |  matches intent StatScoreboard template | proof | 39.4–45.699999999999996s | receipts-count | icon·liquid-chrome | ♪ node_lock | Do that and you stop fighting for clicks and start being the source the answer cites. on-screen: You become the cited source |
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→You become the cited sourcecurate pillar, stats, statsLabels | |||||||
| 8 |  matches intent ProcessFlow template | step | 45.7–52.300000000000004s | kinetic-build | icon·white-knockout | ♪ node_lock | Your move: pick one question your buyers ask, answer it plainly, and wrap it in FAQ schema. on-screen: Your move: one question, one schema block |
expected on screen: red ground · a ProcessFlow panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ProcessFlowvisual pipelineshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Your move: one question, one schema blockcurate stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 52.3–57.8s | coalescence | icon·liquid-chrome | ♪ bed_out | Modern SEO is being the answer, not just a result. Help first, structure second. on-screen: Be the answer, not just a result |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Be the answer, not just a result | |||||||
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)
tiktokSEO in the answer-engine era: stop stuffing keywords. Write the clearest answer to ONE real question, then wrap it in FAQ schema so AI quotes you. Be the answer, not result #11. (AI-assisted.)
instagramBe the answer, not result #11.
Write for the human → mark up with schema → get quoted.
#seo #aeo #contentmarketing #searchstrategy #temerarii
linkedinSEO used to be keyword stuffing for a robot. Now answer engines read for meaning and quote the page that actually helps. The move: write the clearest answer to one real question, then add schema, especially FAQ schema, so each question becomes a block an engine can lift into an answer. Write for the human first, then make it easy for the parser. Takeaway: be the cited source, not result number eleven.
xSEO now: stop stuffing keywords. Write the clearest answer to one real question, wrap it in FAQ schema so AI quotes you. Be the answer, not result #11. temerarii.xyz
facebookSEO used to be stuffing keywords and hoping. Now answer engines read for meaning and quote the page that helps. Write the clearest answer to one real question, then add schema (FAQ schema especially) so each question becomes a block an engine can lift into an answer. Write for the human first, the parser second. Full method on the site.
threadsSEO now: write the clearest answer to one real question, then add FAQ schema so AI engines can quote it. Write for the human first, the parser second. Be the answer, not result #11.
pinterestModern SEO and AEO strategy: write the clearest answer to a real question, then add FAQ schema markup so AI answer engines quote your page. Write for humans first, structure for parsers second. Search engine optimization, answer engine optimization, content strategy.
blueskySEO now: write the clearest answer to one question, wrap it in FAQ schema so AI quotes you. Be the answer, not result #11. temerarii.xyz
youtubeModern SEO: Be the Answer, Not Result #11 (Schema + AEO)
SEO used to be stuffing keywords for a robot. Now answer engines read for meaning and quote the page that actually helps. We break it down: write the clearest answer to one real question, then add schema, especially FAQ schema, so each question becomes a block an engine can lift straight into an answer. Write for the human first, then make it easy for the parser. Be the cited source.
Made with The Big T-M. AI-assisted.
more at temerarii.xyz