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-W34-Mon-3kind threadweek W34date 2026-08-24campaign thread · Monpillar socialbeat Monasset videoduration 49.5sground whitescenes 9

Checklist the per-video bar — engine/sim

86.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review social-W34-Mon-3 good|bad)
⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_sequence_across_assetsdup_set_across_assets · 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 · 49.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–5.0sspatial-parallaxicon·3d-extrude♪ bed_in
Event coordination once lived on sticky notes, a clipboard, and pure adrenaline.
on-screen: Events ran on sticky notes
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · node-graph · spatial-parallax · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape torusground whitetreatment 3d-extrudemotion spatial-parallaxpower summoninstrument summon→Events ran on sticky notes
2s2
matches intent
shared field
signature-3d		hook5.0–10.2skinetic-buildicon·wireframe♪ node_lock
One forgotten loading dock and the whole night quietly falls apart at six.
on-screen: One missed task tanks the night
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape torusground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→One missed task tanks the night
3s3
matches intent
NumberedList
template		teach10.2–15.2skinetic-buildicon·wireframe♪ node_lock
The method: build a minute-by-minute run-of-show with one owner for every line.
on-screen: Build a run-of-show timeline
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape torusground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Build a run-of-show timelinecurate items, nodes
4s4
matches intent
ComparisonTable
template		proof15.2–20.4sreceipts-counticon·wireframe♪ node_lock
When every task had a name, the panicked group texts simply stopped happening.
on-screen: Named owners stopped the chaos
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape torusground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Named owners stopped the chaoscurate colA, colB, rows, statsLabels
5s5
matches intent
CodeWindow
template		diff20.4–26.299999999999997scrossfade-8ficon·wireframe♪ node_lock
Hope is not a plan, and a vibe has never once parked a catering truck.
on-screen: A timeline beats a vibe
expected on screen: white ground · a CodeWindow panel over a dimmed Signal Field · Nuntius leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape torusground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→A timeline beats a vibecurate codeLines, windowTitle
6s6
matches intent
ChecklistCard
template		teach26.3–32.6skinetic-buildicon·wireframe♪ node_lock
Now we hand the AI the event details and it drafts the timeline and the owners.
on-screen: AI drafts the run-of-show
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Nuntius leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape torusground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→AI drafts the run-of-showcurate items, nodes
7s7
matches intent
KpiGrid
template		proof32.6–38.1sreceipts-counticon·wireframe♪ node_lock
We caught the gaps days early instead of at the door with a clipboard.
on-screen: Setup got calmer and faster
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape torusground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Setup got calmer and fastercurate kpis, statsLabels
8s8
matches intent
BlueprintGrid
template		step38.1–44.0skinetic-buildicon·wireframe♪ node_lock
Your step: give every single task a name and a clock, with no orphan jobs.
on-screen: One owner per line
expected on screen: white ground · a BlueprintGrid panel over a dimmed Signal Field · Nuntius leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual pipelineshape torusground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→One owner per linecurate rows, stages, steps
9s9
matches intent
shared field
signature-3d		resolve44.0–49.5scoalescenceicon·3d-extrude♪ bed_out
Soon the plan will reshuffle itself the moment a vendor runs an hour late.
on-screen: Soon it reschedules itself
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→Soon it reschedules itself

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)

tiktokOne forgotten loading dock can tank a whole event. The fix: a minute-by-minute run-of-show with ONE named owner per line. (AI-assisted) We hand AI the event details and it drafts the timeline and owners. A vibe has never parked a catering truck.
instagramEvents used to run on sticky notes + adrenaline. One missed task = the night falls apart. Build a run-of-show. One owner per line. AI drafts it from the details. #eventplanning #eventcoordination #runofshow #eventpros #temerarii
linkedinEvent coordination once lived on sticky notes and pure adrenaline, and one forgotten loading dock can quietly sink the whole night. The method that fixes it: a minute-by-minute run-of-show with one named owner for every line. When every task has a name, the panicked group texts stop. Now we hand AI the event details and it drafts the timeline and the owners, so we catch gaps days early instead of at the door. Takeaway: hope is not a plan, give every task a name and a clock.
xOne forgotten loading dock tanks the whole event. Fix: a minute-by-minute run-of-show, one named owner per line. AI drafts it from the details. A vibe never parked a catering truck. temerarii.xyz
facebookEvent coordination used to run on sticky notes and adrenaline, and one forgotten loading dock can sink the whole night. The fix: a minute-by-minute run-of-show with one named owner per line. When every task has a name, the panicked group texts stop. Now AI drafts the timeline and owners from the event details, so we catch gaps days early. Planning an event? Let's build your run-of-show.
threadsEvents used to run on sticky notes and adrenaline. One forgotten loading dock and the night falls apart. Fix: a minute-by-minute run-of-show, one named owner per line. AI drafts it. A vibe never parked a catering truck.
pinterestEvent coordination that actually holds together: build a minute-by-minute run-of-show with one named owner for every task. No orphan jobs, no panicked group texts. Use AI to draft the timeline from your event details. Event planning, run of show template, event coordination, event management tips.
blueskyOne forgotten loading dock tanks the whole event. Fix: a minute-by-minute run-of-show, one named owner per line. AI drafts it. A vibe never parked a catering truck. temerarii.xyz
youtubeEvent Coordination: A Run-of-Show With One Owner Per Line Event coordination once lived on sticky notes, a clipboard, and pure adrenaline, and one forgotten loading dock can quietly sink the whole night at six. The method that fixes it: a minute-by-minute run-of-show with one named owner for every line. When every task has a name, the panicked group texts stop. Now we hand AI the event details and it drafts the timeline and the owners, so we catch gaps days early instead of at the door. Soon the plan will reshuffle itself the moment a vendor runs late. Your step: give every task a name and a clock, with no orphan jobs. Hope is not a plan. AI-assisted production. More at temerarii.xyz

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

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