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-W38-Thukind longformweek W38date 2026-09-24campaign longform-youtubepillar performancebeat asset videoduration 141.7sground blackscenes 8

Checklist the per-video bar — engine/sim

96.7/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W38-Thu good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_genericgeneric_scene · 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 8 scenes · 141.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–18.4sspatial-parallaxicon·wireframe♪ bed_in
Today is SMS, the channel that prints when you respect it and gets you blocked when you do not. Stop guessing, start printing. By the end you will know how to send texts a model times and writes from real behavior, short, useful, and rare enough that people keep reading.
on-screen: SMS people actually want
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→SMS people actually want
2s2
matches intent
NumberedList
template
teach18.4–39.7skinetic-buildicon·ember-fill♪ node_lock
First, consent. You text only people who clearly said yes, with a plain checkbox they had to tick, kept on record. Have the agent pull your list and flag anyone without a clear opt-in, then drop them. This is not optional and it is not a vibe. Fewer good numbers beat a big list that gets you fined.
on-screen: Get the yes on paper
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Get the yes on papercurate items, nodes
3s3
matches intent
ChecklistCard
template
teach39.7–60.6skinetic-buildicon·wireframe♪ node_lock
A text gets one job. Hand the model the single action you want, confirm the booking, claim the spot, and ask it to write that in under one hundred sixty characters with a link. No paragraph, no two asks. The model is good at cutting. You want the kind of text you yourself would not mind getting.
on-screen: One message, one job
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→One message, one jobcurate items, nodes
4s4
matches intent
CheatSheet
template
teach60.6–82.2skinetic-buildicon·white-knockout♪ node_lock
Now trigger on behavior, like we did with email, but tighter. Booking made, send the confirm by text in seconds through your tool's API, something like Twilio. Pickup ready, send the alert. The agent watches the event and fires the one message that matches. Speed is the whole point of the channel, so let the machine handle the timing.
on-screen: Fire on the moment
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape dodecaground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Fire on the momentcurate nodes, points, uses
5s5
matches intent
FlowSchematic
template
teach82.2–102.4skinetic-buildicon·liquid-chrome♪ node_lock
Set a hard limit. Tell the agent: no more than one text per person per day, and never before eight or after nine. Have it enforce that cap before any send. This is the rule that keeps SMS valuable. The moment it feels like spam, it dies, so you let the model guard the door.
on-screen: Cap it so it stays welcome
expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape dodecaground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Cap it so it stays welcomecurate nodes, stages
6s6
matches intent
TerminalRun
template
teach102.4–119.7skinetic-buildicon·ember-fill♪ node_lock
We hold the same standard with the people who follow the studio. Consent on record, rare sends, real reasons. We would rather text you once with something true than five times with noise. You can see how we treat the audience, and the whole system, at office.temerarii.xyz.
on-screen: We keep our own list clean
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual node-graphshape dodecaground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→We keep our own list cleancurate nodes
7s7
matches intent
RankList
template
proof119.7–136.7sreceipts-counticon·wireframe♪ node_lock
So: keep only clear opt-ins, write one job per text with a model, fire it on the moment, and cap the volume hard. Texts that people welcome are texts that pay. The full setup is live at office.temerarii.xyz. Start with the booking confirm and nothing else.
on-screen: Text rare, true, and on time
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Text rare, true, and on timecurate rows, statsLabels
8s8
first render · fix pending
shared field
signature-3dgeneric_scene
resolve136.7–141.7scoalescenceicon·wireframe♪ bed_out
Performance, demystified: tie every dollar to a result
on-screen: Chapter 7
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Chapter 7

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)

youtubeSend SMS people actually want: short, timed by a model, and rare Text prints when you respect it and gets you blocked when you do not. This is how to send messages a model times and writes from real behavior, short, useful, and rare enough that people keep reading. The method: - Get the yes on paper. Text only people who clearly opted in, with a plain checkbox kept on record. Have the agent flag anyone without a clear opt-in and drop them. This is not optional and not a vibe. - One message, one job. Hand the model the single action you want, confirm the booking or claim the spot, and ask it to write that in under one hundred sixty characters with a link. No paragraph, no two asks. - Fire on the moment. Trigger on behavior: booking made, send the confirm in seconds through your tool's API, something like Twilio. The agent watches the event and fires the one matching message. Speed is the whole point. - Cap it so it stays welcome. Tell the agent no more than one text per person per day, and never before eight or after nine, enforced before any send. The moment it feels like spam, it dies. The honest proof: we hold the same standard with the people who follow the studio. Consent on record, rare sends, real reasons. We would rather text you once with something true than five times with noise. Keep only clear opt-ins, write one job per text with a model, fire it on the moment, and cap the volume hard. Start with the booking confirm and nothing else. The full setup is at office.temerarii.xyz. Keywords: SMS marketing, consent opt-in, Twilio API, triggered messages, message frequency cap.

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