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-W31-Tuekind longformweek W31date 2026-08-04campaign longform-youtubepillar it_devbeat asset videoduration 149.0sground blackscenes 8

Checklist the per-video bar — engine/sim

100.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W31-Tue good|bad)
✓ all static checks pass — one-focal/scene · tier-by-beat · one-track caption · colorway · cast+shape correct · no banned/fabricated. (audio + visual tiers verify on the rendered finals — Phase 2)

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 8 scenes · 149.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–20.2sspatial-parallaxicon·white-knockout♪ bed_in
Cut busywork, keep revenue. Today it is email, the channel everyone overworks and underthinks. Most teams blast everyone and call it a campaign. We are going to show you how to let a model segment your list and write to each group from real behavior. By the end you will send less and keep more.
on-screen: Email that earns its send
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Email that earns its send
2s2
matches intent
ChecklistCard
template
teach20.2–40.0skinetic-buildicon·wireframe♪ node_lock
Step one. Export your list with one extra column, last purchase date. That single field splits buyers from ghosts. A model can read that export and tell you who is warm and who has been gone for a year. Sending the same note to both is the busywork that quietly burns your sender reputation.
on-screen: Stop blasting the whole list
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Stop blasting the whole listcurate items, nodes
3s3
matches intent
NumberedList
template
teach40.0–57.0skinetic-buildicon·wireframe♪ node_lock
Step two. Feed that file to Claude Code and ask it to group people by behavior, recent buyers, lapsed buyers, never bought. The model does the sorting in seconds. You now have three audiences who need three different messages, instead of one message that fits nobody.
on-screen: Let the model build the segments
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let the model build the segmentscurate items, nodes
4s4
matches intent
WireframeMock
template
teach57.0–76.5skinetic-buildicon·wireframe♪ node_lock
Step three. Tell the model to write a short, honest win-back note only for the lapsed group. No discount theater, just a plain reason to come back. Then connect to your email tool, like Resend, through its API so the model can draft and queue it without you copy-pasting into a clunky editor.
on-screen: Write to the lapsed, not the loyal
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write to the lapsed, not the loyalcurate nodes
5s5
matches intent
StackTrace
template
teach76.5–95.6skinetic-buildicon·wireframe♪ node_lock
Step four. Stop sending on a fixed weekly schedule out of habit. Have the model trigger the win-back only when someone crosses ninety days quiet. That is behavior, not calendar. You send when it matters and stay silent when it does not, which is how email keeps making money instead of noise.
on-screen: Time it off real signals
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Time it off real signalscurate errMsg, errType, fix, frames, nodes
6s6
matches intent
TerminalRun
template
teach95.6–113.3skinetic-buildicon·wireframe♪ node_lock
Step five. Ask the model to draft three subject lines for the same note, each with a different angle. Send them to small slices, keep the winner. The model writes the variants fast, so the test costs you minutes. Your gut stops deciding and your list decides instead.
on-screen: Test the subject, not your gut
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Test the subject, not your gutcurate nodes
7s7
matches intent
StatScoreboard
template
proof113.3–131.3sreceipts-counticon·wireframe♪ node_lock
We run our own list on this exact setup. We do not have a fancy email team hiding behind the curtain, just a model reading behavior and writing to segments through an API. We send fewer emails than we used to, and the ones we send actually get opened.
on-screen: We email our own people this way
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→We email our own people this waycurate pillar, stats, statsLabels
8s8
matches intent
shared field
signature-3d
resolve131.3–149.0scoalescenceicon·white-knockout♪ bed_out
So the takeaway. Good email is not volume, it is sending the right note to the right group at the right moment, and letting a model do the sorting and drafting. Less work, more return. See the studio run it in public at office dot temerarii dot xyz.
on-screen: See the whole stack live
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→See the whole stack live

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)

youtubeSegment your email list with a model and write only to the people who left Most teams blast the whole list and call it a campaign. This shows how to let a model split your list by behavior and write a different note to each group, so you send less and keep more. What you learn: - Export your list with one extra column: last purchase date. That single field separates buyers from ghosts. - Feed the file to Claude Code and ask it to group people by behavior: recent buyers, lapsed buyers, never bought. Now you have three audiences instead of one message that fits nobody. - Have the model write a short, honest win-back note for the lapsed group only, then connect to an email tool like Resend through its API so it can draft and queue without copy-pasting. - Trigger the win-back when someone crosses ninety days quiet, not on a fixed weekly schedule. That is behavior, not calendar. - Ask the model for three subject lines, send them to small slices, keep the winner. Your gut stops deciding and your list decides. We run our own list on this exact setup, with a model reading behavior and writing through an API. The point: good email is the right note to the right group at the right moment. See the studio run it in public at office.temerarii.xyz. Keywords: email segmentation, win-back email, Resend API, subject line testing, MCP, Claude Code

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