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-W43-Wedkind longformweek W43date 2026-10-28campaign longform-youtubepillar strategic_relationsbeat asset videoduration 130.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-W43-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 · 130.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–23.0sspatial-parallaxicon·liquid-chrome♪ bed_in
Today is aerial and drone work, and most people treat it like a stunt: fly around, grab whatever looks cool, sort it out later. We do the opposite. The week is the plan behind the proof, so today we plan the flight before the drone leaves the ground. Here is how The Big T-M turns aerial footage into something you can actually use.
on-screen: Drone shots without the chaos
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→Drone shots without the chaos
2s2
matches intent
NumberedList
template
teach23.0–45.7skinetic-buildicon·white-knockout♪ node_lock
The first move is a shot list written as data. Each aerial shot gets a row: the move, the height, the subject, the length in seconds. We keep it in the plan, same as everything else. Now the flight is a checklist, not a hope. You know before takeoff exactly which frames you need, so you stop flying blind and burning battery.
on-screen: Storyboard the flight first
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→Storyboard the flight firstcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach45.7–66.6skinetic-buildicon·liquid-chrome♪ node_lock
Next, tie each aerial shot to a line of the script. If a chapter needs a slow reveal of a building, the plan says so, and the editor knows that clip belongs there. The words decide the pictures. When the plan links footage to lines, assembling the edit is matching a list, not guessing what goes where.
on-screen: Let the script call the cuts
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 script call the cutscurate items, nodes
4s4
matches intent
PipelineMap
template
teach66.6–88.6skinetic-buildicon·white-knockout♪ node_lock
Here is the tool step. Run the raw clips through a video tool that stabilizes shake and applies your color grade automatically, using the same brand tokens as everything else. We script it so every clip gets the same treatment. The drone gives you motion. The code gives you a look that matches the rest of the brand, every time.
on-screen: Stabilize and grade by code
expected on screen: red ground · a PipelineMap panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Stabilize and grade by codecurate nodes, stages
5s5
matches intent
RankList
template
proof88.6–109.89999999999999sreceipts-counticon·liquid-chrome♪ node_lock
The honest proof is that footage planned this way drops straight into the edit and fits. No scrambling, no clip that nobody can place. When the shot list, the script, and the grade all come from one plan, the aerial work behaves. That is the whole point: less drama in the air, more usable frames on the ground.
on-screen: Planned footage proves itself
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→Planned footage proves itselfcurate rows, statsLabels
6s6
matches intent
shared field
signature-3d
resolve109.9–130.4scoalescenceicon·liquid-chrome♪ bed_out
So drone work as a system: storyboard the flight as data, tie each shot to a script line, and stabilize and grade by code. Do that and aerial stops being a gamble. The full plan lives in public at office dot temerarii dot xyz, where you can see how every clip connects back to the words.
on-screen: Plan the air, then fly it
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→Plan the air, then fly it

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 turn access and the right rooms into real results Access is only worth something if you can turn it into something real. This video shows how to make the right rooms work for you, with a system that does the follow through so the access does not go to waste. The method: Decide what one room is for before you walk in. Name the single outcome you want from the relationship, write it down, and let everything else serve that. A room without a job is a nice chat you forget by Friday. Capture what was said, not what you remember. Record or note the real points, then run them through a model that pulls the commitments, the names, and the next steps into a short list. Memory fades, a captured list does not, and the follow through is where most access dies. Make the follow up a system, not a good intention. The model drafts the note, the recap, the next ask, against your real notes from the room, and you send it. The relationship moves because the next step was written down and acted on, not left to a busy week. Keep one record of every room and what came of it. A simple file the rest of your system can read, so you can see which rooms turned into something and which were just noise. That record tells you where to spend the next month. Access becomes real when the boring follow through is automatic. The room opens the door, but the system is what walks through it. See how we wire access into the rest of the machine at office.temerarii.xyz. Keywords: business relationships, networking, follow up, partnerships, CRM, strategic relations.

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