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-W44-Frikind longformweek W44date 2026-11-06campaign longform-youtubepillar performancebeat —asset videoduration 112.9sground 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-W44-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 6 scenes · 112.9s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–19.1sspatial-parallaxicon·white-knockout♪ bed_in
Today is social strategy, the choice nobody makes on purpose: where to even show up. Building presence in public does not mean every app at once. It means one or two done well. Spreading thin is how people quit. Here is how we pick the platform that fits and ignore the noise.
on-screen: Pick the platform, skip the rest
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→Pick the platform, skip the rest
2s2
matches intent
NumberedList
template		teach19.1–39.3skinetic-buildicon·white-knockout♪ node_lock
First step. Do not guess. We use the listening loop, a search tool and a forum reader wired into the agent, to find where our specific people already gather and talk. The platform is not a taste choice. It is wherever the room already meets. Go to the room, do not build a new one.
on-screen: Ask where your people already are
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 where your people already arecurate items, nodes
3s3
matches intent
ChecklistCard
template		teach39.3–59.099999999999994skinetic-buildicon·liquid-chrome♪ node_lock
Second step. Each platform rewards a different shape. One wants threads, one wants vertical video, one wants a long post. We list what we can actually make well and match it to the platform that rewards it. If your best work is writing, you do not start on a video-first app. Play your strength.
on-screen: Match the platform to your format
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→Match the platform to your formatcurate items, nodes
4s4
matches intent
CodeWindow
template		teach59.1–77.9skinetic-buildicon·white-knockout♪ node_lock
Third step. We pick one platform to be the home base and treat the rest as repeats. Make the post once for the home platform, then let the model reshape it for the others later. You build a real foothold in one place before you spread. Narrow first beats thin everywhere.
on-screen: Start narrow, then widen
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Start narrow, then widencurate codeLines, nodes, windowTitle
5s5
matches intent
RankList
template		proof77.9–97.0sreceipts-counticon·liquid-chrome♪ node_lock
The honest proof. We do not chase every app. We post where our actual room meets and let the rest be reruns of the same idea. The whole platform map, and why we chose each one, is laid out for you at office dot temerarii dot xyz. No secret, just the reasoning.
on-screen: We post where our room meets
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape dodecaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We post where our room meetscurate rows, statsLabels
6s6
matches intent
shared field
signature-3d		resolve97.0–112.9scoalescenceicon·white-knockout♪ bed_out
The takeaway. Strategy is mostly subtraction. Find where your people already are, match it to what you make best, win that one room, then widen. Pick your home platform this week, and see how we picked ours at office dot temerarii dot xyz.
on-screen: One room won beats five half-done
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 room won beats five half-done

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)

youtubeHow to measure real lift with receipts instead of vanity metrics Likes and views feel good and tell you nothing about whether the work moved the business. This video shows how to measure real lift with receipts instead of vanity metrics, so you can tell what actually worked. The method: Decide the one real outcome first. Not impressions, the thing that matters, a booking, a reply, a sale. Name it before you publish, so you are measuring against a goal you set, not a number that happens to be high. Tag everything at publish so you can trace it back. Put a simple tag on every link, naming the campaign, the channel, and the week. When a result comes in, the tag tells you which piece earned it. Without the tag, you are guessing. Compare against the right baseline. A number alone means nothing. Hold it next to the same week last year or the week before, so you see the change, not just the level. The arrow up or down is the story, not the raw count. Keep the record honest. Show real numbers or an honest empty state. Never fill a chart with a fabricated figure to look busy. A report that lies trains you to trust the wrong thing and make the wrong call. Tie every channel back to the one outcome. Email, social, the site, all measured against the same goal, so you can see which one actually carried weight and which just made noise. Vanity metrics are a comfort. Receipts are the truth, and the truth is what tells you where to put next month's effort. See how we measure in public at office.temerarii.xyz. Keywords: marketing analytics, attribution, UTM tags, KPIs, vanity metrics, conversion tracking, reporting.

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

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view