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-W39-Tuekind longformweek W39date 2026-09-29campaign longform-youtubepillar staff_trainingbeat asset videoduration 137.7sground whitescenes 7

Checklist the per-video bar — engine/sim

98.2/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W39-Tue 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 7 scenes · 137.7s · 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.7sspatial-parallaxicon·3d-extrude♪ bed_in
The measurable stack, day three. Today is email. Email is the only channel you actually own, and most people waste it blasting everyone the same thing. We are going to make it measurable and personal at the same time. By the end you will know how to segment your list and let a model write to each group from its own behavior.
on-screen: Email that earns the open
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground whitetreatment 3d-extrudemotion spatial-parallaxpower summoninstrument summon→Email that earns the open
2s2
matches intent
NumberedList
template
teach22.7–42.5skinetic-buildicon·wireframe♪ node_lock
First move. Stop sending one email to the whole list. Connect your sending tool, something like Resend, to your agent through its API. Then split your contacts by one real action: who opened last time, who bought, who went quiet. Behavior, not guesses. The split is the work. The writing is the easy part.
on-screen: Split the list by what they did
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Split the list by what they didcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach42.5–60.5skinetic-buildicon·wireframe♪ node_lock
Second move. Feed the agent one segment and its history, then ask for a short email that speaks only to that group. The quiet people get a different message than the buyers. The model writes from what they did, so it sounds like you noticed them, because you did.
on-screen: Write from the segment, not at it
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write from the segment, not at itcurate items, nodes
4s4
matches intent
FlowSchematic
template
teach60.5–80.0skinetic-buildicon·wireframe♪ node_lock
Third move. Have the agent draft two subject lines and send each to a small slice of the segment first. Whichever gets more opens, send to the rest. This is a plain A-B test your tool can run through its API. You are letting the inbox vote before you commit the whole list.
on-screen: Test two subject lines, keep the winner
expected on screen: white ground · a FlowSchematic panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Test two subject lines, keep the winnercurate nodes, stages
5s5
matches intent
NodeGraphCard
template
teach80.0–102.7skinetic-buildicon·wireframe♪ node_lock
Fourth move. Pull the results back into the agent and ask it to look past the open rate at who clicked through and what they did next on the site. An open is polite. A click that ends in a booking is money. Track the chain, not the first step, or you will optimize for people just looking at your subject line.
on-screen: Read the reply, not just the open
expected on screen: white ground · a NodeGraphCard panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual node-graphshape knotground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Read the reply, not just the opencurate hub, nodes
6s6
matches intent
RankList
template
proof102.7–120.0sreceipts-counticon·wireframe♪ node_lock
Proof. We run our own list this way, The Big T-M. Every send teaches the next one, because the results feed straight back into the agent that writes the following email. We are not buying a giant list. We are reading the small one we have, closely.
on-screen: Every send taught the next one
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape knotground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Every send taught the next onecurate rows, statsLabels
7s7
matches intent
shared field
signature-3d
resolve120.0–137.7scoalescenceicon·3d-extrude♪ bed_out
The takeaway. Owned email beats rented attention, but only if you read it. Split your list once, write to one segment from its behavior, and watch the clicks. Do that one send this week. You can see the loop running on us at office dot temerarii dot xyz.
on-screen: Send one segmented email this week
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→Send one segmented email this week

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)

youtubeMake email measurable and personal at the same time with a model Email is the only channel you actually own, and most people waste it blasting everyone the same thing. This is how to segment your list and let a model write to each group from its own behavior. The method: - Split the list by what they did. Connect your sending tool, something like Resend, to your agent through its API, then split contacts by one real action: who opened last time, who bought, who went quiet. The split is the work; the writing is the easy part. - Write from the segment, not at it. Feed the agent one segment and its history, then ask for a short email that speaks only to that group. The quiet people get a different message than the buyers, so it sounds like you noticed them, because you did. - Test two subject lines, keep the winner. Have the agent draft two and send each to a small slice first. Whichever gets more opens, send to the rest, a plain A-B test your tool runs through its API. - Read the reply, not just the open. Pull the results back and look past the open rate at who clicked through and what they did next on the site. Track the chain, not the first step. The honest proof: we run our own list this way. Every send teaches the next one, because the results feed straight back into the agent that writes the following email. We read the small list we have, closely. Owned email beats rented attention, but only if you read it. Split your list once, write to one segment from its behavior, and watch the clicks. Do that one send this week. See the loop on us at office.temerarii.xyz. Keywords: email marketing, segmentation, A/B subject lines, Resend API, click tracking.

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