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-Frikind longformweek W39date 2026-10-02campaign longform-youtubepillar multimediabeat asset videoduration 138.0sground 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-Fri 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 · 138.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.5sspatial-parallaxicon·wireframe♪ bed_in
The measurable stack, day six. Today is copywriting. Most copy is written once, loved by its author, and never tested. We are going to treat words like a thing you can measure and improve. By the end you will know how to write variants, test them against real visitors, and let the winners teach the model.
on-screen: Copy you can A-B prove
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground whitetreatment wireframemotion spatial-parallaxpower summoninstrument summon→Copy you can A-B prove
2s2
matches intent
NumberedList
template
teach20.5–41.8skinetic-buildicon·wireframe♪ node_lock
First move. Start every page with the plain promise, then the proof, in that order. Tell the agent to draft a headline that says what the visitor gets, followed by one honest reason to believe it. No empty hype words, the ones everyone reaches for. Plain promise, real proof. That structure alone beats most copy on the web.
on-screen: Write the promise, then the proof
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Write the promise, then the proofcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach41.8–60.9skinetic-buildicon·wireframe♪ node_lock
Second move. Ask the agent for three versions of the same headline, each true, each said a different way. One blunt, one warm, one specific. You are not looking for clever. You are looking for which true sentence lands. The model is cheap at variations, so make it earn its keep here.
on-screen: Generate three honest variants
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Generate three honest variantscurate items, nodes
4s4
matches intent
CodeWindow
template
teach60.9–81.4skinetic-buildicon·wireframe♪ node_lock
Third move. Run those variants as a live test using a simple split-test tool or your own routing, then send each to a share of real visitors. Track which one ends in the action you care about. The reader picks the winner, not your taste. Your taste is just a guess until the click confirms it.
on-screen: Let visitors pick the words
expected on screen: white ground · a CodeWindow panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let visitors pick the wordscurate codeLines, nodes, windowTitle
5s5
matches intent
LogStream
template
teach81.4–99.80000000000001skinetic-buildicon·wireframe♪ node_lock
Fourth move. Take the winning line and feed it back to the agent as the new example to match. Now the next page starts from what already worked, not from a blank screen. Copy compounds when you keep the proof. Most people throw the winner away and start guessing again.
on-screen: Feed the winner back in
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LogStreamvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Feed the winner back incurate nodes, rows
6s6
matches intent
ComparisonTable
template
proof99.8–120.0sreceipts-counticon·wireframe♪ node_lock
Proof. The lines on our own pages, The Big T-M, are the ones that survived a test, not the ones we fell in love with. We let the visitor decide and we keep the receipt. We will not quote a fake lift. We will tell you the practice: write true, test live, keep the winner.
on-screen: Our headlines earned their spot
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Our headlines earned their spotcurate colA, colB, rows, statsLabels
7s7
matches intent
shared field
signature-3d
resolve120.0–138.0scoalescenceicon·wireframe♪ bed_out
The takeaway. Words are a variable you can measure, so stop treating them as sacred. Write the promise plainly, make three honest variants, test them, and keep what wins. Pick one important headline and test it this week. See our tested copy live at office dot temerarii dot xyz.
on-screen: Test one headline this week
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Test one headline 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)

youtubeTreat your copy like a thing you can A-B prove, not a sacred draft Most copy is written once, loved by its author, and never tested. This is how to write variants, test them against real visitors, and let the winners teach the model. The method: - Write the promise, then the proof, in that order. Have the agent draft a headline that says what the visitor gets, followed by one honest reason to believe it. That structure alone beats most copy on the page. - Generate three honest variants of the same headline, each true, each said a different way: one blunt, one warm, one specific. You are not after clever; you are after which true sentence lands. - Let visitors pick the words. Run the variants as a live test with a simple split-test tool or your own routing, and track which one ends in the action you care about. The reader picks the winner, not your taste. - Feed the winner back in. Give the winning line to the agent as the new example to match, so the next page starts from what worked. Copy compounds when you keep the proof. The honest proof: the lines on our own pages are the ones that survived a test, not the ones we fell in love with. We will not quote a fake lift. The practice is: write true, test live, keep the winner. Write the promise plainly, make three honest variants, test them, and keep what wins. Pick one important headline and test it this week. See our tested copy at office.temerarii.xyz. Keywords: copywriting, A/B testing, headline variants, split testing, conversion copy.

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