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-receipts-W47-Frikind threadweek W47date 2026-11-27campaign thread · Fripillar multimediabeat Friasset videoduration 27.2sground redscenes 5

Checklist the per-video bar — engine/sim

73.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-receipts-W47-Fri good|bad)
⚠ 8 flag(s) — not yet ship-ready: copy_generictoo_complexlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

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

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
KpiGrid
template
stat0–5.1sreceipts-counticon·liquid-chrome♪ node_lock
A hundred personalized outbound emails sent, none of them written by hand.
on-screen: 100 emails. 0 by hand.
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→100 emails. 0 by hand.curate kpis, statsLabels
2s2
first render · fix pending
RankList
templatedead_air
proof5.1–10.1sreceipts-counticon·white-knockout♪ node_lock
Mail-merge templates felt like spam, since the same body went to everyone with just a name swapped in.
on-screen: Merge research + send.
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→Merge research + send.curate rows, statsLabels
3s3
matches intent
StackTrace
template
diff10.1–17.2scrossfade-8ficon·liquid-chrome♪ node_lock
Outbound of the future is personal at scale. Research each contact, draft per person, and send by API.
on-screen: Personal at scale.
expected on screen: red ground · a StackTrace panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual codeshape octaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Personal at scale.curate codeLines, errMsg, errType, fix, frames
4s4
first render · fix pending
BlueprintGrid
templatedead_airgeneric_scene
step17.2–22.2skinetic-buildicon·white-knockout♪ node_lock
Receipts
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual pipelineshape octaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Receiptscurate rows, stages, steps
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve22.2–27.2scoalescenceicon·white-knockout♪ bed_out
Receipts
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→Receipts

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)

tiktok100 personalized outbound emails sent. Zero written by hand. Mail-merge felt like spam because the same body went to everyone. Real method: research each contact, draft per person, send by API. Personal at scale. (AI-assisted)
instagram100 emails. 0 by hand. Mail-merge felt like spam. Same body, swapped name. Real move: research each contact, draft per person, send by API. Personal at scale. #outbound #sales #automation #AI #email
linkedinReceipts: 100 personalized outbound emails sent, none of them written by hand. Mail-merge always felt like spam because the same body went to everyone with a name swapped in. People notice. The method: research each contact, draft a message per person, then send by API. That is outbound that is personal at scale, not a blast. We ran it on our own pipeline first.
xReceipts: 100 personalized outbound emails, 0 written by hand. Mail-merge felt like spam. Real move: research each contact, draft per person, send by API. Personal at scale. temerarii.xyz
facebookHere are the receipts: 100 personalized outbound emails sent, none written by hand. Mail-merge always felt like spam because the same body went to everyone. The method is simpler than it sounds: research each contact, draft a message per person, send by API. See how at temerarii.xyz.
threads100 personalized outbound emails sent. None written by hand. Mail-merge felt like spam because the same body went to everyone with a name swapped in. The real move: research each contact, draft per person, then send by API. Outbound that is personal at scale, not a blast.
pinterestHow to send personalized outbound emails at scale without mail-merge spam: research each contact, draft a unique message per person, then send by API. Receipts from sending 100 personalized cold emails with none written by hand. Outbound sales automation that stays personal.
blueskyReceipts: 100 personalized outbound emails, 0 written by hand. Mail-merge felt like spam. Real move: research each contact, draft per person, send by API. Personal at scale.
youtubeTitle: 100 Personalized Outbound Emails, Zero Written by Hand Mail-merge always felt like spam because the same body went to everyone. We show the method we actually use: research each contact, draft a message per person, then send by API. That is outbound that stays personal at scale. Cold email, outbound sales, automation. temerarii.xyz.

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