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-field-notes-W41-Satkind threadweek W41date 2026-10-17campaign thread · Satpillar performancebeat Satasset videoduration 26.3sground whitescenes 5

Checklist the per-video bar — engine/sim

76.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-field-notes-W41-Sat 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 ListCard
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 · 26.3s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
hook0–6.3skinetic-buildicon·color♪ node_lock
Field note. Your follow-up email was three paragraphs of pressure. The one-liner gets the reply.
on-screen: Your follow-up was a wall
expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Your follow-up was a wall
2s2
first render · fix pending
NumberedList
templatedead_air
teach6.3–11.3skinetic-buildicon·color♪ node_lock
Old follow-ups restated the whole pitch, so the reader hit a wall of text and a reason to wait.
on-screen: One line, easy to answer
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→One line, easy to answercurate items, nodes
3s3
matches intent
LogStream
template
diff11.3–16.3scrossfade-8ficon·color♪ node_lock
Cut your next follow-up to one sentence that ends in an easy yes-or-no question they can answer in seconds.
on-screen: Shrink your next follow-up
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·color logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual codeshape dodecaground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Shrink your next follow-upcurate codeLines, rows
4s4
first render · fix pending
FlowSchematic
templatedead_airgeneric_scene
proof16.3–21.3sreceipts-counticon·color♪ node_lock
Field Notes
expected on screen: white ground · a FlowSchematic panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual receiptsshape dodecaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Field Notescurate stages, statsLabels
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve21.3–26.3scoalescenceicon·3d-extrude♪ bed_out
Field Notes
expected on screen: white ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→Field Notes

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)

tiktokField note: your follow-up email was three paragraphs of pressure. The one-liner gets the reply. Cut it to one sentence that ends in an easy yes-or-no question. (AI-assisted)
instagramField note. Your follow-up was a wall of text. The one-liner gets the reply. Cut it to one sentence. End with an easy question. #sales #followup #coldemail #fieldnotes #temerarii
linkedinField note: your follow-up email was three paragraphs of pressure. The one-liner is what gets the reply. Legacy follow-ups restated the whole pitch, which gives the reader a wall of text and a reason to wait. The fix is small. Cut the next follow-up to one sentence that ends in an easy question, the kind someone can answer in a few seconds. Less to read, lower effort to respond, more replies. Shrink the ask.
xField note: your follow-up was three paragraphs of pressure. The one-liner gets the reply. Cut it to one sentence ending in an easy question. temerarii.xyz
facebookField note from the trenches: your follow-up email was three paragraphs of pressure, and the one-liner is what actually gets the reply. Legacy follow-ups restate the whole pitch. Instead, cut your next one to a single sentence that ends in an easy question. Try it on your next send. More at temerarii.xyz.
threadsField note: your follow-up email was three paragraphs of pressure. The one-liner gets the reply. Legacy follow-ups restated the whole pitch. Cut the next one to one sentence ending in an easy question. Less to read, more replies.
pinterestSales follow-up tip: stop restating the whole pitch. A short one-line follow-up that ends in an easy question gets more replies than three paragraphs of pressure. How to shrink your next follow-up email and lower the effort to respond.
blueskyField note: your follow-up was three paragraphs of pressure. The one-liner gets the reply. Cut it to one sentence ending in an easy question.
youtubeTitle: Field Note: The One-Line Follow-Up That Gets Replies Your follow-up email was three paragraphs of pressure, and the one-liner is what gets the reply. Legacy follow-ups restate the whole pitch and hand the reader a wall of text. The fix: cut your next follow-up to a single sentence that ends in an easy question someone can answer in seconds. Less to read, lower effort to respond, more replies.

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