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-Frikind longformweek W43date 2026-10-30campaign longform-youtubepillar performancebeat asset videoduration 165.5sground blackscenes 8

Checklist the per-video bar — engine/sim

98.4/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review longform-W43-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 8 scenes · 165.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·wireframe♪ bed_in
Today is live streaming, the scariest kind of proof because there is no second take. The week is the plan behind the proof, and going live is the loudest proof of all. So today we plan the stream so the live part is the only thing left to chance. Here is how The Big T-M runs a stream that does not fall apart.
on-screen: Live, but not unplanned
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→Live, but not unplanned
2s2
matches intent
NumberedList
template
teach23.0–47.5skinetic-buildicon·wireframe♪ node_lock
The first move is a run of show: a timed list of segments, what happens, in what order, for how long. We keep it in the plan like everything else. Live does not mean unscripted. It means the script has to hold up in real time. When you have a run of show, dead air has nowhere to hide, because the next thing is always already decided.
on-screen: Script the run of show
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Script the run of showcurate items, nodes
3s3
matches intent
ChecklistCard
template
teach47.5–68.8skinetic-buildicon·wireframe♪ node_lock
Next, build your lower thirds and graphics from the same brand tokens as the rest of your content, the colors and fonts in a file. The overlay reads those values, so your stream looks like your brand without anyone hand-styling it under pressure. Set it once in the plan, and every live show wears the same face automatically.
on-screen: Wire your overlays from tokens
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Wire your overlays from tokenscurate items, nodes
4s4
matches intent
CheatSheet
template
teach68.8–92.9skinetic-buildicon·wireframe♪ node_lock
Here is the tool step that saves the most time. After the stream, run a script that slices the recording into clips at the segment marks from your run of show. A video tool cuts on those timestamps and you wake up to a folder of ready pieces. The live show plans its own highlight reel, because the segments were marked before you went on air.
on-screen: Automate the post-stream cut
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Automate the post-stream cutcurate nodes, points, uses
5s5
matches intent
BlueprintGrid
template
teach92.9–114.9skinetic-buildicon·wireframe♪ node_lock
Then pull the live chat into text and hand it to the model. It pulls out the real questions and the moments people reacted to. That becomes your follow-up content and your next stream's plan. The audience tells you what worked, in their own words, and the model turns that noise into a short list you can actually act on.
on-screen: Capture the chat as data
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Capture the chat as datacurate nodes, rows
6s6
matches intent
FlowSchematic
template
teach114.9–133.70000000000002skinetic-buildicon·wireframe♪ node_lock
The proof is in the calm. A stream with a run of show, token-built overlays, and an automated cut does not turn into a panic. The plan absorbs the pressure so the live moment can breathe. That is the trade: do the boring planning, and the scary part stops being scary.
on-screen: A planned stream behaves
expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→A planned stream behavescurate nodes, stages
7s7
matches intent
StatScoreboard
template
proof133.7–147.79999999999998sreceipts-counticon·wireframe♪ node_lock
And it is the same plan running everything else this week. The stream is just another row in the file, with its own beats and its own job, checked the same way as the scripts and the photos.
on-screen: This is the same one plan
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→This is the same one plancurate pillar, stats, statsLabels
8s8
matches intent
shared field
signature-3d
resolve147.8–165.5scoalescenceicon·wireframe♪ bed_out
So live streaming as a system: script the run of show, wire overlays from tokens, automate the post-stream cut, and capture the chat as data. Do that and live becomes the easy part. See how the whole week is planned in public at office dot temerarii dot xyz.
on-screen: Plan the stream, then go live
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Plan the stream, then go live

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 plan a live stream so the live part is the only thing left to chance Live streaming is the scariest kind of proof because there is no second take. This video shows how to plan the stream so the live part is the only thing left to chance, and the boring planning absorbs the pressure. The method: Script the run of show. A timed list of segments, what happens, in what order, for how long. Live does not mean unscripted. It means the script has to hold up in real time. When you have a run of show, dead air has nowhere to hide, because the next thing is always already decided. Wire your overlays from tokens. Build your lower thirds and graphics from the same brand tokens as the rest of your content, the colors and fonts in a file. The overlay reads those values, so your stream looks like your brand without anyone hand styling it under pressure. Set it once, and every show wears the same face. Automate the post stream cut. After the stream, run a script that slices the recording into clips at the segment marks from your run of show. A video tool cuts on those timestamps and you wake up to a folder of ready pieces. The show plans its own highlight reel. Capture the chat as data. Pull the live chat into text and hand it to the model. It pulls out the real questions and the moments people reacted to, and that becomes your follow up content and your next stream's plan. A stream with a run of show, token built overlays, and an automated cut does not turn into a panic. Do the boring planning, and the scary part stops being scary. See how the whole week is planned in public at office.temerarii.xyz. Keywords: live streaming, run of show, brand tokens, stream overlays, content repurposing, planning.

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