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-W28-Wed-2kind threadweek W28date 2026-07-15campaign thread · Wedpillar multimediabeat Wedasset videoduration 48.0sground redscenes 9

Checklist the per-video bar — engine/sim

98.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W28-Wed-2 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 · 48.0s · 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.5sspatial-parallaxicon·white-knockout♪ bed_in
Interviews used to mean a list of scripted questions read in a stiff order.
on-screen: Interviews meant scripted questions
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Interviews meant scripted questions
2s2
matches intent
shared field
signature-3d		hook5.5–11.0skinetic-buildicon·white-knockout♪ node_lock
You stuck to the script and missed the one answer worth the whole show.
on-screen: You missed the real answer
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→You missed the real answer
3s3
matches intent
NumberedList
template		teach11.0–16.2skinetic-buildicon·liquid-chrome♪ node_lock
The move is deep prep, then the courage to follow the surprising answer.
on-screen: Prep the guest, then follow up
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→Prep the guest, then follow upcurate items, nodes
4s4
matches intent
ComparisonTable
template		proof16.2–22.1sreceipts-counticon·white-knockout♪ node_lock
Read everything the guest ever said so you can ask the question nobody else did.
on-screen: Read everything they ever said
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Read everything they ever saidcurate colA, colB, rows, statsLabels
5s5
matches intent
JsonDiff
template		diff22.1–27.1scrossfade-8ficon·liquid-chrome♪ node_lock
The difference is real listening beats your tidy list of questions.
on-screen: Listening beats your question list
expected on screen: red ground · a JsonDiff panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id JsonDiffvisual codeshape octaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Listening beats your question listcurate codeLines, fileName, lines
6s6
matches intent
ChecklistCard
template		teach27.1–33.0skinetic-buildicon·white-knockout♪ node_lock
Leave a beat of silence and let the guest fill it with the real thing.
on-screen: Leave silence after the answer
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→Leave silence after the answercurate items, nodes
7s7
matches intent
KpiGrid
template		proof33.0–38.0sreceipts-counticon·liquid-chrome♪ node_lock
The follow-up question, not the planned one, is usually the whole interview.
on-screen: The follow-up is the whole show
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape octaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→The follow-up is the whole showcurate kpis, statsLabels
8s8
matches intent
LegacyCard
template		step38.0–43.0skinetic-buildicon·white-knockout♪ node_lock
Your step: over-prep, then be willing to drop a planned question mid-talk.
on-screen: Your step: prep, then drop a question
expected on screen: red ground · a LegacyCard panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id LegacyCardvisual pipelineshape octaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Your step: prep, then drop a questioncurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve43.0–48.0scoalescenceicon·white-knockout♪ bed_out
A good interview listens more than it reads.
on-screen: Interviews that actually listen
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Interviews that actually listen

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 do an interview that doesn't suck (AI-assisted prep): over-prep by reading everything the guest ever said, then have the courage to follow the surprising answer. leave silence. the follow-up is the whole show. #interview #podcasting #contentcreator
instagramScripted questions kill interviews. Over-prep, then follow the answer. Leave silence after they speak. The follow-up is the whole show. #interview #podcast #contentcreator #storytelling #media
linkedinTakeaway: great interviews come from deep prep plus the courage to abandon the script. Read everything the guest ever said so you can ask the question nobody else did, then leave a beat of silence and let them fill it. The follow-up question, not the planned one, is usually the whole show. A good interview listens more than it reads.
xInterview tip: scripted questions kill it. Over-prep, then follow the surprising answer. Leave silence after they speak. The follow-up is the whole show. temerarii.com
facebookInterviews used to mean reading scripted questions in a stiff order, and you missed the one answer worth the whole show. The move is deep prep, then the courage to follow the surprising answer and leave a beat of silence. More at temerarii.com.
threadsScripted questions kill interviews. Over-prep by reading everything the guest ever said, then follow the surprising answer. Leave silence after they speak. The follow-up is the whole show.
pinterestHow to conduct a great interview: deep guest prep, follow-up questions, using silence, abandoning the script. Podcasting tips, interview techniques, content creation, storytelling, better conversations.
blueskyInterview tip: scripted questions kill it. Over-prep, then follow the surprising answer. Leave silence after they speak. The follow-up is the whole show. temerarii.com
youtubeInterviews: Over-Prep, Then Drop The Script Interviews used to mean a list of scripted questions read in a stiff order, so you stuck to the script and missed the one answer worth the whole show. This short shows the move: read everything the guest ever said so you can ask the question nobody else did, then have the courage to follow the surprising answer. Leave a beat of silence and let them fill it. The follow-up question, not the planned one, is usually the whole interview. More at temerarii.com.

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

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