Event Coordination — social-W26-Sun-1 — Temerarii Media Back Office

post social-W26-Sun-1kind threadweek W26date 2026-06-28campaign thread · Sunpillar strategic_relationsbeat Sunasset videoduration 73.0sground whitescenes 9

Checklist the per-video bar — engine/sim

94.1/100

plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness

quantitative quality · weights learn from your reviews (engine.sim.memory review social-W26-Sun-1 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 · 73.0s · comp_id + rendered still + tier + the script

#	Layer (comp_id · still · tier)	Beat	Timecode	Motion	Logo	Audio	VO / on-screen / caption
1	still pending matches intent shared field signature-3d	open	0–7.7s	spatial-parallax	icon·wireframe	♪ bed_in	Running an event used to mean a fat binder, a wall of sticky notes, and one human praying nobody no-shows. on-screen: Events used to mean binders
	expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground whitetreatment wireframemotion spatial-parallaxpower summoninstrument summon→Events used to mean binders
2	still pending matches intent shared field signature-3d	hook	7.7–14.7s	kinetic-build	icon·color	♪ node_lock	The part that always broke first was the schedule, because every speaker change rippled into forty other rows. on-screen: The schedule always broke first
	expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→The schedule always broke first
3	still pending matches intent NumberedList template	teach	14.7–23.5s	kinetic-build	icon·color	♪ node_lock	Here is the real old method: you build a master grid in a sheet, one column per room, one row per time block. on-screen: Old way: master grid by hand
	expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Old way: master grid by handcurate items, nodes
4	still pending matches intent RankList template	proof	23.5–31.6s	receipts-count	icon·color	♪ node_lock	Then you color each cell by status, confirmed, pending, or dropped, so the gaps scream at you before the guests do. on-screen: Color cells by status
	expected on screen: white ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape tetraground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Color cells by statuscurate rows, statsLabels
5	still pending matches intent TerminalRun template	diff	31.6–40.0s	crossfade-8f	icon·color	♪ node_lock	Here is what makes us odd: we trust the conflict list more than the pretty calendar, because conflicts are where money leaks. on-screen: We trust the conflict, not the calendar
	expected on screen: white ground · a TerminalRun panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id TerminalRunvisual codeshape tetraground whitetreatment colormotion crossfade-8fpower morphinstrument morph→We trust the conflict, not the calendarcurate codeLines
6	still pending matches intent ChecklistCard template	teach	40.0–48.4s	kinetic-build	icon·color	♪ node_lock	So write one rule per shared resource, a mic, a room, a person, that flags any two bookings touching the same slot. on-screen: Write a clash rule per resource
	expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Write a clash rule per resourcecurate items, nodes
7	still pending matches intent StatScoreboard template	proof	48.4–56.8s	receipts-count	icon·color	♪ node_lock	We caught a double-booked room at one client's setup because the rule lit red the second both names landed in one cell. on-screen: Double-booked room caught at setup
	expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape tetraground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Double-booked room caught at setupcurate pillar, stats, statsLabels
8	still pending matches intent StepFlow template	step	56.8–64.89999999999999s	kinetic-build	icon·color	♪ node_lock	Your step today: one grid, one clash rule, one named owner per row, and you have killed most of the chaos. on-screen: Step: one grid, one rule, one owner
	expected on screen: white ground · a StepFlow panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id StepFlowvisual pipelineshape tetraground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Step: one grid, one rule, one ownercurate stages, steps
9	still pending matches intent shared field signature-3d	resolve	64.9–73.0s	coalescence	icon·wireframe	♪ bed_out	Coordination is not charisma, it is kept promises in a grid, and that is the boring thing The Big T-M sells. on-screen: Coordination is just kept promises
	expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Coordination is just kept promises

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)

tiktokWhy your event always falls apart at setup (it's the schedule). The old binder method, the conflict-list trick we actually trust, and the one clash rule that caught a double-booked room. AI-assisted, human-built. Coordination is kept promises, not charisma.

instagramEvents don't break from bad vibes. They break from one schedule cell nobody owned. The fix: one grid, one clash rule, one owner per row. That's the whole job. #eventplanning #eventproduction #operations #projectmanagement #temerarii

linkedinEvent coordination rarely fails on charisma. It fails on a schedule cell that two bookings quietly share. The method we use: build a master grid (one column per room, one row per time block), color cells by status, then write one clash rule per shared resource — a mic, a room, a person. The rule lights red the moment two names touch the same slot. We caught a double-booked room at a client setup that way. Takeaway: assign one named owner per row and most of the chaos disappears before guests arrive.

xEvents don't break from bad vibes. They break from one schedule cell two bookings quietly share. Grid + one clash rule per resource + one owner per row. That's coordination. temerarii.com

facebookRunning an event used to mean a fat binder and one human praying nobody no-shows. The schedule always broke first. Here's the boring fix that works: build a master grid, color each cell by status, and write one clash rule per shared resource so a double-booked room lights up red before setup day. Want the grid template? Reply EVENT and we'll send it over.

threadsEvents don't fall apart from bad vibes. They fall apart from one schedule cell nobody owned. Master grid + one clash rule per shared resource (mic, room, person) + one owner per row. A double-booked room lights red before guests show. Coordination is kept promises, not charisma.

pinterestEvent coordination checklist: how to build a master event schedule grid, color-code booking status (confirmed, pending, dropped), and write a clash rule per shared resource to catch double-booked rooms before setup. Event planning template, event production workflow, conference scheduling, run of show, resource conflict tracking.

blueskyEvents don't break from bad vibes. They break from one schedule cell two bookings quietly share. Grid + one clash rule per resource + one owner per row. That's the whole job. temerarii.com

youtubeEvent Coordination: The Clash Rule That Saves Your Setup Day Running an event used to mean a binder and a prayer. The schedule always broke first. In this short we walk the real method: build a master grid (one column per room, one row per time block), color cells by status, and write one clash rule per shared resource — a mic, a room, a person — so a double-booked room lights red before guests arrive. Do this today: one grid, one clash rule, one named owner per row. Coordination is kept promises, not charisma. AI-assisted, human-built 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