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-Thukind longformweek W39date 2026-10-01campaign longform-youtubepillar performancebeat asset videoduration 121.8sground 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-W39-Thu 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 · 121.8s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–21.3sspatial-parallaxicon·white-knockout♪ bed_in
The measurable stack, day five. Today is text messages. SMS gets opened almost every time, which is exactly why it is easy to abuse. We are going to use it with respect and still measure it. By the end you will know how to send the right text at the right moment and prove it actually moved someone.
on-screen: SMS: short, timed, measured
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→SMS: short, timed, measured
2s2
matches intent
NumberedList
template
teach21.3–42.900000000000006skinetic-buildicon·white-knockout♪ node_lock
First move. Only text people who clearly said yes, and keep the proof. Use a tool like Twilio through its API and log every opt-in with a timestamp. This is not just polite, it is the law in most places. A clean consent list is the foundation. Everything you measure after this only counts if this part is honest.
on-screen: Get real consent, keep the record
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→Get real consent, keep the recordcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach42.9–64.5skinetic-buildicon·liquid-chrome♪ node_lock
Second move. Tie the text to something the person did, not to a date you picked. A cart left behind, a booking an hour away. Wire the agent to watch for that event and fire the message through the API. A text that arrives because of what you just did feels like service. A random blast feels like spam.
on-screen: Trigger on action, not on a calendar
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→Trigger on action, not on a calendarcurate items, nodes
4s4
matches intent
AnnotatedDiagram
template
teach64.5–83.6skinetic-buildicon·white-knockout♪ node_lock
Third move. Put exactly one tagged link in the message and give it one job. Confirm the booking, finish the order. Tag it so you can trace the click back, same UTM trick as the ads. A text with three asks gets none of them done. One clear move, one trackable link.
on-screen: One link, one job
expected on screen: red ground · a AnnotatedDiagram panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→One link, one jobcurate callouts, nodes
5s5
matches intent
ListCard
template
proof83.6–102.69999999999999sreceipts-counticon·liquid-chrome♪ node_lock
Proof. When we use SMS for ourselves, The Big T-M, it only fires on a real trigger, never on a whim. The message points to one thing and we can see whether the person took it. We are not padding a number. We are sending fewer texts that each have a reason.
on-screen: We text only on a trigger
expected on screen: red ground · a ListCard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We text only on a triggercurate items, statsLabels
6s6
matches intent
shared field
signature-3d
resolve102.7–121.80000000000001scoalescenceicon·white-knockout♪ bed_out
The takeaway. Text is powerful because it is intimate, so use it rarely and track it fully. Get consent, fire on a real action, send one tagged link, and read the result. Set up one triggered message this week. You can see how we handle it at office dot temerarii dot xyz.
on-screen: One triggered text, fully traced
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→One triggered text, fully traced

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)

youtubeUse SMS with respect and still measure it: short, timed, and traced Text gets opened almost every time, which is exactly why it is easy to abuse. This is how to send the right message at the right moment and prove it actually moved someone. The method: - Get real consent and keep the record. Use a tool like Twilio through its API and log every opt-in with a timestamp. This is the law in most places, and everything you measure after only counts if this part is honest. - Trigger on action, not a calendar. Tie the text to something the person did, a cart left behind, a booking an hour away. Wire the agent to watch for that event and fire the message. A text that arrives because of what you just did feels like service. - One link, one job. Put exactly one tagged link in the message, give it one job, confirm the booking or finish the order, and tag it so you can trace the click back, the same UTM trick as ads. Three asks get none of them done. The honest proof: when we use SMS for ourselves, it only fires on a real trigger, never on a whim. The message points to one thing and we can see whether the person took it. We are sending fewer texts that each have a reason. Text is intimate, so use it rarely and track it fully. Get consent, fire on a real action, send one tagged link, and read the result. Set up one triggered message this week. See how we handle it at office.temerarii.xyz. Keywords: SMS marketing, Twilio API, consent, triggered messages, UTM tracking.

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