Event Coordination — topic-sr-events — Temerarii Media Back Office

post topic-sr-eventskind topicweek —date —campaign strategic-relations-pillarpillar strategic_relationsbeat —asset videoduration 59.4sground blackscenes 9

Checklist the per-video bar — engine/sim

93.3/100

plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness

quantitative quality · weights learn from your reviews (engine.sim.memory review topic-sr-events good|bad)

⚠ 3 flag(s) — not yet ship-ready: too_complexcurate_missinggeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SceneReel

9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending

▶ open rendered mp4

expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 9 scenes · 59.4s · 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–6.6s	spatial-parallax	icon·liquid-chrome	♪ —	An event is just a hard deadline surrounded by people, and most of the chaos is information that lives in the wrong on-screen: An event is a deadline with people
	expected on screen: black ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground blacktreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→three-mark
2	still pending first render · fix pending LegacyCard templatecurate_missing	legacy	6.6–13.2s	crossfade-8f	icon·ember-fill	♪ —	The old way ran the whole thing off one fragile spreadsheet and a thread of texts nobody could find by show day. on-screen: The old way: a spreadsheet and hope
	expected on screen: black ground · a LegacyCard panel over a dimmed Signal Field · Nexus leads · crossfade-8f · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id LegacyCardshape tetraground blacktreatment ember-fillmotion crossfade-8fpower morphinstrument decay→three-symbolic
3	still pending matches intent NumberedList template	teach	13.2–20.299999999999997s	kinetic-build	icon·wireframe	♪ —	We put guests, vendors, and run-of-show in a single Airtable base, so every change has exactly one home. on-screen: One source of truth in Airtable
	expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
4	still pending matches intent ChecklistCard template	teach	20.3–26.4s	kinetic-build	icon·white-knockout	♪ —	We write a run-of-show down to the minute, because a vague timeline is where events quietly fall apart. on-screen: Build a minute-by-minute run sheet
	expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground blacktreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5	still pending matches intent TerminalRun template	teach	26.4–34.7s	kinetic-build	icon·liquid-chrome	♪ —	Reminders fire automatically — confirmations, call times, vendor pings — wired from the base so no one has to remember to remember. on-screen: Automate the reminders
	expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id TerminalRunvisual node-graphshape tetraground blacktreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes
6	still pending matches intent CodeWindow template	teach	34.7–40.900000000000006s	kinetic-build	icon·ember-fill	♪ —	Every task gets one named owner, so when something slips there is no debate about whose it was. on-screen: Assign one owner per task
	expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual node-graphshape tetraground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate codeLines, nodes, windowTitle
7	still pending first render · fix pending KpiGrid templategeneric_scene	proof	40.9–48.1s	receipts-count	icon·wireframe	♪ —	Running our last event this way, every cue hit on time across roughly forty tracked tasks. (placeholder figures) on-screen: 0 missed cues across 40 tasks
	expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape tetraground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate kpis, statsLabels
8	still pending matches intent shared field signature-3d	futurist	48.1–54.4s	spatial-parallax	icon·white-knockout	♪ —	Next we are putting the run sheet on a live dashboard the whole team watches in real time during the show. on-screen: Soon: live event dashboard
	expected on screen: black ground · tetra hero in the shared Signal Field · Nexus leads · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldshape tetraground blacktreatment white-knockoutmotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
9	still pending matches intent shared field signature-3d	resolve	54.4–59.4s	coalescence	icon·liquid-chrome	♪ swell	The full base and run-sheet template is yours to copy. on-screen: The event system · temerarii.xyz
	expected on screen: black ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground blacktreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→three-coalescence

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 12 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBlueskyEmailSMSBlog

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

tiktokAn event is just a hard deadline surrounded by people, and most of the chaos is information living in the wrong place. Here's the system. Put guests, vendors, and run-of-show in one Airtable base, so every change has exactly one home. Write the run sheet down to the minute. Wire reminders to fire automatically, confirmations and call times and vendor pings. Give every task one named owner. (AI-assisted) temerarii.xyz

instagramAn event is a hard deadline surrounded by people. Most of the chaos is information in the wrong place. One Airtable base for guests, vendors, run-of-show. A run sheet down to the minute. Reminders that fire on their own. One named owner per task. A vague timeline is where events quietly fall apart. #eventplanning #runofshow #airtable #eventops #temerarii

linkedinAn event is just a hard deadline surrounded by people, and most of the chaos is information that lives in the wrong place. The old way ran the whole thing off one fragile spreadsheet and a thread of texts nobody could find by show day. The system: - Put guests, vendors, and run-of-show in a single Airtable base, so every change has exactly one home - Write a run-of-show down to the minute, because a vague timeline is where events quietly fall apart - Wire reminders to fire automatically: confirmations, call times, vendor pings, so no one has to remember to remember - Give every task one named owner, so when something slips there is no debate about whose it was The full base and run-sheet template is yours to copy. temerarii.xyz

xAn event is a hard deadline surrounded by people, and most of the chaos is info in the wrong place. Put guests, vendors, and run-of-show in one Airtable base. Run sheet to the minute. Auto reminders. One owner per task. temerarii.xyz

facebookAn event is just a hard deadline surrounded by people, and most of the chaos is information living in the wrong place. The old way ran on one fragile spreadsheet and a text thread nobody could find by show day. Here is the system. Put guests, vendors, and run-of-show in a single Airtable base, so every change has one home. Write the run sheet down to the minute. Wire reminders to fire automatically: confirmations, call times, vendor pings. Give every task one named owner, so nothing slips into a debate about whose job it was. The full base and run-sheet template is yours to copy. temerarii.xyz

threadsAn event is just a hard deadline surrounded by people, and most of the chaos is info living in the wrong place. The system: one Airtable base for guests, vendors, and run-of-show. A run sheet down to the minute. Reminders that fire on their own. One named owner per task. A vague timeline is where events quietly fall apart.

pinterestRun an event without the spreadsheet panic: the system. Put guests, vendors, and run-of-show in one Airtable base so every change has a single home. Write a run-of-show down to the minute. Wire automatic reminders for confirmations, call times, and vendor pings. Assign one named owner per task. A copyable event operations template that keeps every cue on time. temerarii.xyz

blueskyAn event is a hard deadline surrounded by people, and most of the chaos is info in the wrong place. One Airtable base for guests, vendors, run-of-show. Run sheet to the minute. Auto reminders. One owner per task. temerarii.xyz

youtubeRun an Event From One Airtable Base: The Operations System, Given Away An event is just a hard deadline surrounded by people, and most of the chaos is information that lives in the wrong place. The old way ran on one fragile spreadsheet and a text thread nobody could find by show day. Here is the system. The steps: - Put guests, vendors, and run-of-show in a single Airtable base, so every change has exactly one home - Write a run-of-show down to the minute, because a vague timeline is where events quietly fall apart - Wire reminders to fire automatically: confirmations, call times, and vendor pings, from the base - Give every task one named owner, so when something slips there is no debate about whose it was What is next: the run sheet goes on a live dashboard the whole team watches in real time during the show. The full base and run-sheet template is yours to copy 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