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 longform-W37-Satkind longformweek W37date 2026-09-19campaign longform-youtubepillar performancebeat asset videoduration 124.2sground redscenes 6

Checklist the per-video bar — engine/sim

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

Composition comp · template family · expected output

composition LongFormChaptersfamily / template LongFormChapters
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 6 scenes · 124.2s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–22.0sspatial-parallaxicon·white-knockout♪ bed_in
Today closes the week on partnership outreach: actually reaching the people your listening surfaced. Finding the right partner is half the job. The other half is the note that gets a reply. You will learn how to use your own data to write outreach that does not feel cold, because it is built from something the other side already said.
on-screen: Outreach without the cold
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Outreach without the cold
2s2
matches intent
NumberedList
template
teach22.0–41.8skinetic-buildicon·white-knockout♪ node_lock
First move. For each partner candidate, have Claude pull one real, specific thing they posted recently, and open the note with it. Not flattery. A fact. People can smell a template in one line. A first sentence that proves you actually saw their work is the difference between a reply and the trash folder.
on-screen: Open with a true detail
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Open with a true detailcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach41.8–61.599999999999994skinetic-buildicon·liquid-chrome♪ node_lock
Second move. Have the model frame the ask as a tiny first step, not a marriage. A single shared post. One swapped mention. A short call. Small asks get yes because saying yes is cheap. You can grow it later. Leading with a big proposal to a stranger is how outreach dies on arrival.
on-screen: Ask for one small test
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Ask for one small testcurate items, nodes
4s4
matches intent
BlueprintGrid
template
teach61.6–83.2skinetic-buildicon·white-knockout♪ node_lock
Third move. Log who you contacted, when, and what they said in one file the model can read. Then have it tell you who to follow up with and who to drop. Most replies come on the second touch, not the first. Without a record you forget to follow up, and the follow-up is where the deals actually live.
on-screen: Track every send in one file
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Track every send in one filecurate nodes, rows
5s5
matches intent
KpiGrid
template
proof83.2–103.7sreceipts-counticon·liquid-chrome♪ node_lock
Honest proof: our own outreach starts from a real detail in someone's feed, logged in a file, followed up on schedule. No bought list, no spray. When we say small asks get answered, it is because the small ones are the ones that come back to us. We are running our own playbook in the open.
on-screen: We send ours from data too
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We send ours from data toocurate kpis, statsLabels
6s6
matches intent
shared field
signature-3d
resolve103.7–124.2scoalescenceicon·white-knockout♪ bed_out
The takeaway: warm outreach is just a true opening, a small ask, and a kept record. That is the whole game. Your next step is small. Take the one partner your data ranked first, find one real thing they posted, and write three honest sentences. The full flow is live at office dot temerarii dot xyz.
on-screen: Send one at office.temerarii.xyz
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Send one at office.temerarii.xyz

Format stack 1 aspects · same scenes[], re-cropped

16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 2 destinations

YouTubeBlog

Social captions supplemental published copy · per channel (comp_id level)

youtubeWrite partnership outreach from data so it never feels cold Finding the right partner is half the job. The other half is the note that gets a reply. This is how to use your own data to write outreach built from something the other side already said. The method: - Open with a true detail. For each candidate, have Claude pull one real, specific thing they posted recently and open with it. Not flattery, a fact. A first sentence that proves you saw their work is the difference between a reply and the trash folder. - Ask for one small test, not a marriage. A single shared post, one swapped mention, a short call. Small asks get yes because saying yes is cheap. You can grow it later. - Track every send in one file. Log who you contacted, when, and what they said, then have the model tell you who to follow up with and who to drop. Most replies come on the second touch, and that is where the deals live. The honest proof: our own outreach starts from a real detail in someone's feed, logged in a file, followed up on schedule. No bought list, no spray. The small asks are the ones that come back. Warm outreach is just a true opening, a small ask, and a kept record. Take the partner your data ranked first, find one real thing they posted, and write three honest sentences. The full flow is at office.temerarii.xyz. Keywords: partnership outreach, cold email alternative, warm pitch, follow-up tracking.

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