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-W37-Wedkind longformweek W37date 2026-09-16campaign longform-youtubepillar strategic_relationsbeat asset videoduration 121.5sground 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-W37-Wed 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 · 121.5s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–23.0sspatial-parallaxicon·liquid-chrome♪ bed_in
This one is about event coordination, the live end of strategic relations. Most events fail because someone guessed at the topic. We are going to do it backward. You will learn how to read your audience first, find the gathering they already wish existed, and only then plan it. Listening picks the room so you do not pay to fill an empty one.
on-screen: Build the room they want
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Build the room they want
2s2
matches intent
NumberedList
template
teach23.0–42.5skinetic-buildicon·white-knockout♪ node_lock
First move. In your listening file, have Claude search for posts where people ask if anything exists, or wish there were a place to talk about your topic. Those sentences are unmet demand. When a dozen people independently wish for the same room, you do not need a survey. You need a date.
on-screen: Search for the missing meetup
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Search for the missing meetupcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach42.5–62.3skinetic-buildicon·liquid-chrome♪ node_lock
Second move. Pull the questions people keep asking and never getting answered. Group them with the model into three or four themes. That is your agenda, written by the room before the room exists. An event built from real unanswered questions fills itself, because people show up for the answer they have been chasing.
on-screen: Let the questions write the agenda
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Let the questions write the agendacurate items, nodes
4s4
matches intent
StepFlow
template
teach62.3–81.1skinetic-buildicon·white-knockout♪ node_lock
Third move. Ask the model to count location words in your mentions. If one place keeps coming up, start there. Online works too, but a real city signal tells you where a small in-person gathering would not echo in an empty hall. Let the data pick the dot on the map.
on-screen: Find the city in the noise
expected on screen: red ground · a StepFlow panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Find the city in the noisecurate nodes, steps
5s5
matches intent
RankList
template
proof81.1–101.3sreceipts-counticon·liquid-chrome♪ node_lock
Honest proof: we do not invent topics for our own events. We read what people keep asking and hand them the session. The whole public calendar you are watching was built from a source file the same way, by listening first and deciding second. We are running the studio in the open, this move included.
on-screen: We plan the calendar the same way
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We plan the calendar the same waycurate rows, statsLabels
6s6
matches intent
shared field
signature-3d
resolve101.3–121.5scoalescenceicon·liquid-chrome♪ bed_out
The takeaway: never plan an event in a vacuum. Read the wish, steal the agenda from real questions, follow the location signal, then send one invite. Your next step is small. Search your mentions for the words I wish there were, and read what people answer. See the rest at office dot temerarii dot xyz.
on-screen: Pick a date at office.temerarii.xyz
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Pick a date at office.temerarii.xyz

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)

youtubePlan an event your audience already wants by reading them first Most events fail because someone guessed at the topic. We do it backward: read your audience first, find the gathering they already wish existed, and only then plan it. Listening picks the room so you do not pay to fill an empty one. The method: - Search for the missing meetup. In your listening file, have Claude search for posts where people ask if anything exists, or wish there were a place to talk about your topic. When a dozen people independently wish for the same room, you need a date, not a survey. - Let the questions write the agenda. Pull the questions people keep asking and never getting answered, then group them into three or four themes. An event built from real unanswered questions fills itself. - Find the city in the noise. Have the model count location words in your mentions. If one place keeps coming up, start there. Online works too, but a real city signal tells you where a small gathering would not echo in an empty hall. The honest proof: we do not invent topics for our own events. We read what people keep asking and hand them the session. The whole public calendar was built this way, by listening first and deciding second. Search your mentions for the words I wish there were, and read what people answer. See the rest at office.temerarii.xyz. Keywords: event planning, audience research, unmet demand, meetup strategy.

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