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-W51-Thukind longformweek W51date 2026-12-24campaign longform-youtubepillar performancebeat asset videoduration 116.4sground 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-W51-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 · 116.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–21.6sspatial-parallaxicon·white-knockout♪ bed_in
The week is data fluency for marketers, and today is the lab where data becomes a decision. A dashboard is not a decision. Plenty of teams stare at charts and still do nothing. By the end of this you will know how to run a short weekly habit that turns your numbers into one clear thing to do next.
on-screen: Turn dashboards into decisions
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→Turn dashboards into decisions
2s2
matches intent
NumberedList
template
teach21.6–41.8skinetic-buildicon·white-knockout♪ node_lock
First move: every week, ask the model one question against your live data, what changed since last week and why. It reads the rows and tells you what moved. You are training the team to look for change, not just totals. A number that moved is a clue. A number that sat still is noise.
on-screen: Ask: what changed this week
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→Ask: what changed this weekcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach41.8–62.3skinetic-buildicon·liquid-chrome♪ node_lock
Second move: force a single choice. You tell the model, based on that change, give me one thing to do this week and the reason. Not a list of ten. One. The team learns that the point of data is to pick a next move, and a list of ten is just hiding from the decision.
on-screen: Make it pick one action
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→Make it pick one actioncurate items, nodes
4s4
matches intent
BlueprintGrid
template
teach62.3–81.4skinetic-buildicon·white-knockout♪ node_lock
Third move: before you do the thing, write down what you expect to happen. The model can hold that note. Next week you compare what happened to what you guessed. This is how a team gets calibrated, slowly learning when their read on the data is right and when it is wrong.
on-screen: Write the bet before you act
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Write the bet before you actcurate nodes, rows
5s5
matches intent
CodeWindow
template
proof81.4–99.80000000000001sreceipts-counticon·liquid-chrome♪ node_lock
Honest proof: this weekly loop is how our own studio decides what to build next, off one source file. No made-up lift numbers. The proof is that the calendar in front of you exists because every week we asked what changed, picked one move, and wrote the bet down first.
on-screen: We run this weekly on ourselves
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We run this weekly on ourselvescurate codeLines, statsLabels, windowTitle
6s6
matches intent
shared field
signature-3d
resolve99.8–116.4scoalescenceicon·white-knockout♪ bed_out
So the takeaway is a habit, not a tool: each week, ask what changed, make the model pick one action, and write your bet before you act. Do that and your dashboard finally earns its place. Watch the habit run on live work at office.temerarii.xyz.
on-screen: Make the weekly habit yours
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→Make the weekly habit yours

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)

youtubeTurn dashboards into decisions: a weekly habit that picks one move A dashboard is not a decision. Plenty of teams stare at charts and still do nothing. By the end of this video you will know a short weekly habit that turns your numbers into one clear thing to do next. The habit: - Ask what changed this week. Every week, ask the model one question against your live data: what changed since last week and why. It reads the rows and tells you what moved. Look for change, not just totals. A number that moved is a clue; a number that sat still is noise. - Make it pick one action. Force a single choice. Tell the model, based on that change, give me one thing to do this week and the reason. Not a list of ten. One. The point of data is to pick a next move, and a list of ten is just hiding from the decision. - Write the bet before you act. Before you do the thing, write down what you expect to happen. The model can hold that note. Next week you compare what happened to what you guessed. That is how a team gets calibrated, slowly learning when their read on the data is right. The honest proof: this weekly loop is how our own studio decides what to build next, off one source file. No made-up lift numbers. The proof is that the calendar in front of you exists because every week we asked what changed, picked one move, and wrote the bet down first. The takeaway is a habit, not a tool. Do it and your dashboard finally earns its place. Watch the habit run on live work at office.temerarii.xyz Keywords: turn data into decisions, weekly review habit, what changed this week, pick one action, write the bet, calibrated decisions

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