Back Office · office.temerarii.xyz
One published post, granular — the Social for W37 Mon, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW37-Mon-social-1kindSocialweekW37dayMondate2026-09-14campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

Social Listening
copy ready · render pending

Output-policy spec format · dimensions (asset_specs.output_policy)

formatnative cut · 9:16 · 1:1 · 16:9 dims1080×1920 · 1080×1080 · 1920×1080 cadence5/day floor × 9 channels

Channels 9 destinations

TikTokInstagramLinkedInX/TwitterFacebookThreadsPinterestBlueskyYouTube

This post a distinct social asset — its own angle, storyboard, and cuts

social-W37-Mon-1
5-distinct-social/day · 9:16 master → 1:1 / 16:9 cuts per channel

Channel-cuts this asset → 9 native captions (one master · per-platform aspect+copy)

ChannelNative caption
TiktokEvent planning hack: stop keeping ten versions of the schedule. Build ONE run of show as the single source of truth, link every vendor and cue, then let AI scan for clashes before the day. AI-assisted. #eventplanning #eventcoordinator #events #eventprofs #planning
InstagramOne run of show. One source of truth. Let AI catch the clashes. #eventplanning #eventprofs #eventcoordinator #events #planning
LinkedinEvent coordination breaks when there are ten copies of the schedule and no agreement on which is right. The method: build one run of show as the single source of truth, link every vendor time, room, and cue back to it, then let AI scan for conflicts like a speaker double-booked or a session with no host. Catching a clash days early beats discovering it live. Calm events come from one document, not heroic saves.
XEvent planning: kill the ten schedule copies. One run of show as source of truth, link every cue, let AI scan for clashes. Catch it early. temerarii.com
FacebookEvent coordination used to mean ten versions of the schedule and a phone glued to your ear. Build one run of show as the single source of truth, link every vendor, and let AI flag clashes before the day. Learn how at temerarii.com.
ThreadsEvent planning truth: ten copies of the schedule means zero agreement. Build one run of show as the source of truth, link every cue, let AI scan for clashes. Catch the double-booked speaker on Tuesday, not live in the room.
PinterestEvent coordination method: build one run of show as a single source of truth, link all vendors and cues, use AI to catch scheduling clashes early. Event planning tips, event management, run of show template.
BlueskyEvent planning: one run of show as the source of truth, link every cue, let AI catch clashes before the day. Calm beats heroic saves. temerarii.com
YoutubeThe One-Document Event Planning Method (Plus AI Clash Detection) Events fall apart when ten schedule copies disagree. We cover building a single run of show as the source of truth, linking every vendor and cue, and using AI to scan for conflicts before the day arrives. AI-assisted. More at temerarii.com. #EventPlanning #EventCoordination #EventProfs

Composition layer × scene 9 scenes · this post's OWN storyboard (distinct per asset)

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–6.6sspatial-parallaxicon·ember-fill♪ bed_in
Event coordination used to live in a spreadsheet, a binder, and a phone glued to your ear.
on-screen: Event planning lived in spreadsheets
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape torusground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Event planning lived in spreadsheets
2s2
matches intent
shared field
signature-3d		hook6.6–13.2skinetic-buildicon·wireframe♪ node_lock
The pain everyone hides: one schedule change and you re-typed the entire run of show by hand.
on-screen: One change broke the whole plan
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 change broke the whole plan
3s3
matches intent
NumberedList
template		teach13.2–20.9skinetic-buildicon·wireframe♪ node_lock
Here is the real method: make one run of show the single source of truth, and link everything to it.
on-screen: Make the run of show the source
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→Make the run of show the sourcecurate items, nodes
4s4
matches intent
ComparisonTable
template		proof20.9–27.2sreceipts-counticon·wireframe♪ node_lock
Every vendor time, every room, every cue points back to that one document, not ten copies.
on-screen: Vendors and timing in one place
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→Vendors and timing in one placecurate colA, colB, rows, statsLabels
5s5
matches intent
BuildLog
template		diff27.2–32.7scrossfade-8ficon·wireframe♪ node_lock
The old way had ten copies and zero agreement on which one was right.
on-screen: Old way: ten copies, one truth lost
expected on screen: white ground · a BuildLog panel over a dimmed Signal Field · Nuntius leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual codeshape torusground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Old way: ten copies, one truth lostcurate codeLines, lines
6s6
matches intent
ChecklistCard
template		teach32.7–40.800000000000004skinetic-buildicon·wireframe♪ node_lock
Now AI reads the run of show and flags clashes, the speaker booked in two rooms, the gap with no host.
on-screen: Now AI watches for clashes
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→Now AI watches for clashescurate items, nodes
7s7
matches intent
KpiGrid
template		proof40.8–46.3sreceipts-counticon·wireframe♪ node_lock
Catching a clash on Tuesday beats discovering it live in front of a room.
on-screen: Catch the clash before the day
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→Catch the clash before the daycurate kpis, statsLabels
8s8
matches intent
ListCard
template		step46.3–54.0skinetic-buildicon·wireframe♪ node_lock
Your move: build one run of show, link every vendor, let AI scan for conflicts, brief the team off it.
on-screen: Steps: one doc, link, scan, brief
expected on screen: white ground · a ListCard panel over a dimmed Signal Field · Nuntius leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual pipelineshape torusground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Steps: one doc, link, scan, briefcurate items, stages, steps
9s9
matches intent
shared field
signature-3d		resolve54.0–59.5scoalescenceicon·ember-fill♪ bed_out
That is how The Big T-M runs calm events instead of heroic last-minute saves.
on-screen: Calm events, not heroic saves
expected on screen: white ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Calm events, not heroic saves

Cross-links this post in the day's output set

→ Day (full output set) → Source video → Media (audience preview) → Calendar→ Storyboard hub