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-Satkind longformweek W39date 2026-10-03campaign longform-youtubepillar it_devbeat asset videoduration 155.4sground 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-W39-Sat good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_genericcustom_element_dup · 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 · 155.4s · 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·white-knockout♪ bed_in
The measurable stack, day seven. All week we built the parts: analytics, search, email, ads, text, copy. Today is the spine that holds them together, strategy. Without it you have six tools and no map. By the end you will know how to tie every channel to one revenue number so nothing operates in the dark.
on-screen: The spine that holds the stack
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→The spine that holds the stack
2s2
matches intent
NumberedList
template
teach20.5–38.9skinetic-buildicon·wireframe♪ node_lock
First move. Choose the single number the whole business answers to. For most, it is paid revenue or booked jobs. Write it down. Every channel from this week now has to explain how it moved that one number. A strategy with five goals is five excuses. One number forces honesty.
on-screen: Pick the one north-star number
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→Pick the one north-star numbercurate items, nodes
3s3
first render · fix pending
ChecklistCard
templatecustom_element_dup
teach38.9–58.0skinetic-buildicon·wireframe♪ node_lock
Second move. Pull all six channels into one table your agent can read: the analytics export, the search data, the email results, the ad spend, the SMS clicks, the copy tests. One place. Now the agent can compare them side by side instead of you flipping between six tabs that never agree.
on-screen: Put every channel in one table
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→Put every channel in one tablecurate items, nodes
4s4
matches intent
LegacyCard
template
teach58.0–79.3skinetic-buildicon·wireframe♪ node_lock
Third move. Build a simple attribution view. For each sale, ask the agent to trace the first channel that brought the person and the last one that closed them, using the UTM tags and session ids you set all week. Now you can see which channels open doors and which ones shut deals. They are rarely the same.
on-screen: Map each click to its first touch
expected on screen: black ground · a LegacyCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LegacyCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Map each click to its first touchcurate nodes
5s5
matches intent
StepFlow
template
teach79.3–97.69999999999999skinetic-buildicon·wireframe♪ node_lock
Fourth move. With everything in one view, have the agent rank channels by cost per the north-star number and recommend where the next dollar should go. This is the whole point of measuring. Not to admire numbers, but to move money toward what pays and away from what does not.
on-screen: Move budget toward what pays
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Move budget toward what payscurate nodes, steps
6s6
matches intent
WireframeMock
template
teach97.7–116.80000000000001skinetic-buildicon·wireframe♪ node_lock
Fifth move. Save the entire combined table to a dated file every week. That snapshot is your record. When you change strategy, you compare against the real past, not a story you tell yourself later. The agent can diff this week against last in seconds and show you only what truly shifted.
on-screen: Snapshot the whole stack weekly
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→Snapshot the whole stack weeklycurate nodes
7s7
matches intent
KpiGrid
template
proof116.8–135.6sreceipts-counticon·wireframe♪ node_lock
Proof. Everything you watched this week, The Big T-M runs from one source file, read by one agent, the same way this strategy reads your channels. We are not showing you a slide of a system. We are running the system in public, in plain sight, without inventing a single number.
on-screen: Our whole calendar runs from one file
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Our whole calendar runs from one filecurate kpis, statsLabels
8s8
matches intent
shared field
signature-3d
resolve135.6–155.4scoalescenceicon·white-knockout♪ bed_out
The takeaway. A measurable stack is not six dashboards. It is one north-star number, one combined table, and one model that reads it and tells you where to move. Pick your one number this week and pull your channels into a single view. Watch our whole stack run at office dot temerarii dot xyz.
on-screen: One number, one table, one agent
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→One number, one table, one agent

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)

youtubeTie every marketing channel to one revenue number with one table and one model All week we built the parts: analytics, search, email, ads, text, copy. Without a spine you have six tools and no map. This is how to tie every channel to one revenue number so nothing operates in the dark. The method: - Pick the one north-star number the whole business answers to, for most paid revenue or booked jobs. Every channel now has to explain how it moved that one number. A strategy with five goals is five excuses. - Put every channel in one table the agent can read: the analytics export, the search data, email results, ad spend, SMS clicks, copy tests. Now it compares them side by side instead of you flipping between six tabs that never agree. - Map each click to its first touch. For each sale, ask the agent to trace the first channel that brought the person and the last that closed them, using the UTM tags and session ids you set all week. The opener and the closer are rarely the same. - Move budget toward what pays. Have the agent rank channels by cost per the north-star number and recommend where the next dollar should go. The point of measuring is to move money, not admire it. - Snapshot the whole stack weekly to a dated file. When you change strategy, you compare against the real past, not a story you tell yourself later. The honest proof: everything you watched this week runs from one source file, read by one agent, the same way this strategy reads your channels. We run the system in public, without inventing a number. A measurable stack is one north-star number, one combined table, and one model that reads it. Pick your one number this week and pull your channels into a single view. Watch our whole stack at office.temerarii.xyz. Keywords: marketing strategy, revenue attribution, UTM tracking, channel comparison, north-star metric.

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