Social Listening — social-W37-Mon-1 — Temerarii Media Back Office

post social-W37-Mon-1kind threadweek W37date 2026-09-14campaign thread · Monpillar socialbeat Monasset videoduration 59.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-W37-Mon-1 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 · 59.5s · 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·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
2	still pending matches intent shared field signature-3d	hook	6.6–13.2s	kinetic-build	icon·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
3	still pending matches intent NumberedList template	teach	13.2–20.9s	kinetic-build	icon·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
4	still pending matches intent ComparisonTable template	proof	20.9–27.2s	receipts-count	icon·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
5	still pending matches intent BuildLog template	diff	27.2–32.7s	crossfade-8f	icon·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
6	still pending matches intent ChecklistCard template	teach	32.7–40.800000000000004s	kinetic-build	icon·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
7	still pending matches intent KpiGrid template	proof	40.8–46.3s	receipts-count	icon·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
8	still pending matches intent ListCard template	step	46.3–54.0s	kinetic-build	icon·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
9	still pending matches intent shared field signature-3d	resolve	54.0–59.5s	coalescence	icon·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

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)

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

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

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