Back Office · office.temerarii.xyz
One asset, all the way in — composition, the wireframe + storyboard, the output format stack, and the template, all read from the SAME content-index record. The expected output matches what /media surfaces for this post.
post social-W25-Tue-3kind threadweek W25date 2026-06-23campaign thread · Tuepillar performancebeat Tueasset videoduration 46.9sground blackscenes 9

Checklist the per-video bar — engine/sim

98.5/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W25-Tue-3 good|bad)
⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel
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 · 46.9s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–5.2sspatial-parallaxicon·ember-fill♪ bed_in
The old way of SEO stuffed pages with keywords and hoped Google noticed.
on-screen: SEO used to mean stuff in keywords
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→SEO used to mean stuff in keywords
2s2
matches intent
shared field
signature-3d		hook5.2–10.2skinetic-buildicon·wireframe♪ node_lock
It barely worked then, and it stopped working a long time ago.
on-screen: That never really worked well
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→That never really worked well
3s3
matches intent
NumberedList
template		teach10.2–15.2skinetic-buildicon·wireframe♪ node_lock
The fix that holds: make each page answer one clear question fully.
on-screen: Answer one clear question per page
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Answer one clear question per pagecurate items, nodes
4s4
matches intent
ComparisonTable
template		proof15.2–20.7sreceipts-counticon·wireframe♪ node_lock
Set the page title as the exact question someone would type to find it.
on-screen: Page title is the question itself
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Page title is the question itselfcurate colA, colB, rows, statsLabels
5s5
matches intent
CodeWindow
template		diff20.7–25.7scrossfade-8ficon·wireframe♪ node_lock
Matching the word is not enough. Match what the searcher actually wants.
on-screen: Match intent, not just the word
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape dodecaground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Match intent, not just the wordcurate codeLines, windowTitle
6s6
matches intent
ChecklistCard
template		teach25.7–31.2skinetic-buildicon·wireframe♪ node_lock
Now we let a model list every related question a reader would ask next.
on-screen: Now AI maps related questions fast
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Now AI maps related questions fastcurate items, nodes
7s7
matches intent
KpiGrid
template		proof31.2–36.7sreceipts-counticon·wireframe♪ node_lock
We answer those follow-ups on the same page, so it covers the whole need.
on-screen: Cover the follow-ups on one page
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Cover the follow-ups on one pagecurate kpis, statsLabels
8s8
matches intent
PipelineMap
template		step36.7–41.7skinetic-buildicon·wireframe♪ node_lock
One page, one clear question, every honest follow-up answered below it.
on-screen: One page, one question, all follow-ups
expected on screen: black ground · a PipelineMap panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual pipelineshape dodecaground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→One page, one question, all follow-upscurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve41.7–46.900000000000006scoalescenceicon·ember-fill♪ bed_out
The Big T-M writes for the question behind the search, not the keyword.
on-screen: The Big T-M answers intent, not keywords
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→The Big T-M answers intent, not keywords

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 that still works (AI-assisted): stop stuffing keywords. Make each page answer one clear question fully, with the title BEING the question. Let AI list the follow-up questions and answer those too. #seo #marketing #contentmarketing
instagramKeyword stuffing is dead. Answer one clear question per page. Make the title the question. #seo #contentmarketing #marketing #searchengineoptimization #google
linkedinKeyword stuffing stopped working long ago. The method that holds: make each page answer one clear question fully and set the title as the exact question searchers type. The takeaway: match intent, not just the word. Let a model list the natural follow-up questions and answer those on the same page.
xSEO isn't keyword stuffing. Make each page answer one clear question, title = the question, then cover the follow-ups. temerarii.xyz
facebookStuffing keywords never really worked. What does: make each page answer one clear question fully, with the title being the question itself, then cover the follow-ups. AI helps map those. Read it on the site.
threadsSEO truth: keyword stuffing is dead. Make each page answer one clear question, set the title as that question, then answer the follow-ups. Match intent, not just the word.
pinterestSEO method that works: stop stuffing keywords and make each page answer one clear question fully, with the title as the question itself. Then cover the follow-up questions. SEO tips, content marketing, search optimization.
blueskySEO isn't keyword stuffing. Answer one clear question per page, title = the question, cover the follow-ups. temerarii.xyz
youtubeSEO Without Keyword Stuffing: Answer the Question Stuffing keywords stopped working long ago. We show the method that holds: make each page answer one clear question fully, set the title as the exact question searchers type, and match intent, not just the word. Then let a model list the natural follow-up questions and answer those on the same page.

Cross-links every lens is a view on this one record

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view