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 social-W26-Thu-3kind threadweek W26date 2026-07-02campaign thread · Thupillar multimediabeat Thuasset videoduration 76.7sground blackscenes 9

Checklist the per-video bar — engine/sim

91.7/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W26-Thu-3 good|bad)
⚠ 2 flag(s) — not yet ship-ready: copy_generictoo_complex · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SignalFieldReel
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 9 scenes · 76.7s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–7.7sspatial-parallaxicon·white-knockout♪ bed_in
Live streaming used to be a prayer to the internet gods: one camera, one shaky connection, and zero second chances.
on-screen: Live streaming used to be a prayer
expected on screen: black ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Live streaming used to be a prayer
2s2
matches intent
shared field
signature-3d		hook7.7–15.4skinetic-buildicon·ember-fill♪ node_lock
And of course the stream always froze at the exact moment something good happened, because the bandwidth had other plans.
on-screen: The stream dies the moment it matters
expected on screen: black ground · octa hero in the shared Signal Field · Lumen leads · mark · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape octaground blacktreatment ember-fillmotion kinetic-buildpower laser-lockinstrument laser-trace→The stream dies the moment it matters
3s3
matches intent
NumberedList
template		teach15.4–23.1skinetic-buildicon·wireframe♪ node_lock
Here is the old discipline that never dies: always have a wired connection ready, because wifi is a fair-weather friend.
on-screen: Old rule: keep a wired backup
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape octaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Old rule: keep a wired backupcurate items, nodes
4s4
matches intent
ComparisonTable
template		proof23.1–32.900000000000006sreceipts-counticon·white-knockout♪ node_lock
The method: set your bitrate to what your upload can actually carry, not what looks nice, because a smooth low stream beats a frozen pretty one.
on-screen: Stream at the bitrate your line can
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Stream at the bitrate your line can holdcurate colA, colB, rows, statsLabels
5s5
matches intent
StackTrace
template		diff32.9–42.4scrossfade-8ficon·liquid-chrome♪ node_lock
Our rule: rehearse the failure, not only the show, so when the feed drops you have a slate, a sorry, and a plan B ready.
on-screen: We rehearse the failure, not just the
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual codeshape octaground blacktreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→We rehearse the failure, not just the showcurate codeLines, errMsg, errType, fix, frames
6s6
matches intent
ChecklistCard
template		teach42.4–50.8skinetic-buildicon·ember-fill♪ node_lock
Always record a clean local copy while you broadcast, because the stream is the live gift but the recording is the asset.
on-screen: Record locally while you stream
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→Record locally while you streamcurate items, nodes
7s7
matches intent
KpiGrid
template		proof50.8–59.199999999999996sreceipts-counticon·wireframe♪ node_lock
We had a client feed hiccup once, swapped to the wired backup in seconds, and the audience never even noticed the stumble.
on-screen: A drop the audience never noticed
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape octaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→A drop the audience never noticedcurate kpis, statsLabels
8s8
matches intent
PipelineMap
template		step59.2–68.3skinetic-buildicon·white-knockout♪ node_lock
Your step before your next stream: run a wire, cap your bitrate to your real upload, and hit local record as well as live.
on-screen: Step
expected on screen: black ground · a PipelineMap panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual pipelineshape octaground blacktreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Step: wire it, cap the bitrate, record localcurate stages, steps
9s9
matches intent
shared field
signature-3d		resolve68.3–76.7scoalescenceicon·white-knockout♪ bed_out
Live looks like luck but it is really just calm planning, and that calm under pressure is what The Big T-M brings.
on-screen: Live is calm planning, not luck
expected on screen: black ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Live is calm planning, not luck

Format stack 3 aspects · same scenes[], re-cropped

9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 9 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky

Social captions supplemental published copy · per channel (comp_id level)

tiktokYour live stream froze at the best moment because wifi is a fair-weather friend. The fix: run a WIRED backup, cap your bitrate to what your upload can actually hold, and record a clean local copy while you broadcast. We swapped to wired in seconds — audience never noticed.
instagramLive looks like luck. It's really calm planning. Run a wired backup. Cap bitrate to your real upload. Record locally while you stream. #livestreaming #liveproduction #broadcast #streaming #temerarii
linkedinLive streaming used to be a prayer to the internet gods — one camera, one shaky connection, zero second chances. And the stream always froze at the exact moment something good happened. The discipline that never dies: always have a wired connection ready, because wifi is a fair-weather friend. Set your bitrate to what your upload can actually carry, not what looks nice — a smooth low stream beats a frozen pretty one. Rehearse the failure, not just the show, so when the feed drops you have a slate and a plan B. And always record a clean local copy while you broadcast: the stream is the live gift, but the recording is the asset. We had a client feed hiccup once, swapped to the wired backup in seconds, and the audience never noticed. Live looks like luck; it's really calm planning.
xYour live stream froze at the best moment because wifi is a fair-weather friend. Wired backup. Cap bitrate to your real upload. Record locally while you stream. We swapped to wired in seconds — nobody noticed. temerarii.com
facebookLive streaming used to be a prayer — one camera, one shaky connection, zero second chances. And the stream always froze the moment something good happened. The discipline that never dies: run a wired backup, cap your bitrate to what your upload can actually carry, and record a clean local copy while you broadcast. We had a client feed hiccup once, swapped to wired in seconds, and the audience never noticed. Planning a live event? Let's make it bulletproof.
threadsYour live stream froze at the best moment because wifi is a fair-weather friend. Run a wired backup. Cap your bitrate to what your upload can actually hold. Record a clean local copy while you broadcast. We swapped to wired in seconds — the audience never noticed. Live is calm planning, not luck.
pinterestLive streaming setup tips: use a wired backup connection, cap your bitrate to your real upload speed, rehearse the failure, and record a local copy while broadcasting. Live streaming guide, broadcast production, OBS setup, streaming reliability, live event tech.
blueskyYour live stream froze at the best moment because wifi is a fair-weather friend. Wired backup. Cap bitrate to your real upload. Record locally while you stream. We swapped to wired in seconds — nobody noticed. temerarii.com
youtubeLive Streaming: Calm Planning, Not Luck Live streaming used to be a prayer to the internet gods — one camera, one shaky connection, zero second chances. And the stream always froze the moment something good happened. The discipline that never dies: always have a wired connection ready, set your bitrate to what your upload can actually carry (a smooth low stream beats a frozen pretty one), rehearse the failure not just the show, and record a clean local copy while you broadcast. We had a client feed hiccup once, swapped to wired in seconds, and the audience never noticed. Live looks like luck; it's really calm planning — by The Big T-M.

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

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