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 thread-ask-the-operator-W45-Tuekind threadweek W45date 2026-11-10campaign thread · Tuepillar multimediabeat Tueasset videoduration 25.0sground whitescenes 5

Checklist the per-video bar — engine/sim

76.7/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-ask-the-operator-W45-Tue good|bad)
⚠ 7 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template LowerThird
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 5 scenes · 25.0s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
hook0–5.0skinetic-buildicon·wireframe♪ node_lock
Email question: my unsubscribes went up. Did I do something wrong?
on-screen: "Unsubscribes spiking"
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape octaground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→"Unsubscribes spiking"
2s2
first render · fix pending
NumberedList
templatedead_air
teach5.0–10.0skinetic-buildicon·wireframe♪ node_lock
Most times it is how often you send, not what you say. A jump in sends is the first thing to check.
on-screen: Cadence beats content
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Cadence beats contentcurate items, nodes
3s3
matches intent
ComparisonTable
template
proof10.0–15.0sreceipts-counticon·wireframe♪ node_lock
Take folks who have not opened in sixty days. Put them on a slower send this week.
on-screen: Slow the cold ones
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Slow the cold onescurate colA, colB, rows, statsLabels
4s4
first render · fix pending
SchematicCard
templatedead_airgeneric_scene
step15.0–20.0skinetic-buildicon·wireframe♪ node_lock
Ask the Operator
expected on screen: white ground · a SchematicCard panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual pipelineshape octaground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Ask the Operatorcurate nodes, stages, steps
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve20.0–25.0scoalescenceicon·ember-fill♪ bed_out
Ask the Operator
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Ask the Operator

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)

tiktokReader asks: my unsubscribes jumped, did I do something wrong? Usually it's how often you send, not what you say. Move readers who haven't opened in sixty days to a slower schedule this week and watch the rate settle. (AI-assisted)
instagramAsk the operator: "Unsubscribes spiking." My unsubscribes jumped. Did I mess up? Usually it's cadence, not content. Move cold readers (60+ days no open) to a slower send. Watch the rate settle. #emailmarketing #newsletter #deliverability #marketing #askanything
linkedinReader question: my unsubscribes jumped, did I do something wrong? Usually it's cadence, not content. A spike in send volume is the first thing to check before you rewrite anything. The move: take readers who haven't opened in sixty days and put them on a lighter send this week. You stop annoying the disengaged, your unsubscribe rate settles, and your engaged readers still hear from you on the normal schedule.
xReader: my unsubscribes jumped, what went wrong? Usually it's cadence, not content. Move readers who haven't opened in 60 days to a lighter send this week and watch the rate settle. temerarii.xyz
facebookA reader wrote in: my unsubscribes jumped, did I do something wrong? Usually it's how often you send, not what you say. The fix: take readers who haven't opened in sixty days and move them to a lighter schedule this week. You stop bothering the disengaged and your unsubscribe rate settles. More answers at temerarii.xyz
threadsAsk the operator. "My unsubscribes jumped. Did I do something wrong?" Usually it's cadence, not content. A jump in how often you send is the first thing to check. Move readers who haven't opened in 60 days to a lighter send this week.
pinterestWhy your email unsubscribes spiked, and how to fix it: usually it's send cadence, not content. Move readers who haven't opened in sixty days to a lighter schedule to settle your unsubscribe rate. Email marketing tips, newsletter cadence, list re-engagement.
blueskyReader: my unsubscribes jumped, what went wrong? Usually it's cadence, not content. Move readers who haven't opened in 60 days to a lighter send this week and watch the rate settle.
youtubeTitle: Why Your Email Unsubscribes Spiked (Fix the Cadence) Reader question: my unsubscribes jumped, did I do something wrong? Usually it's cadence, not content. A jump in send volume is the first thing to check. The move: take readers who haven't opened in sixty days and put them on a lighter send this week. You stop annoying the disengaged and your unsubscribe rate settles.

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