Social — W35 Sun — Temerarii Media Back Office

postW35-Sun-social-2kindSocialweekW35daySundate2026-08-30campaignalways-oncadence5/day floor × 9 channels

Copy the published post text

Screenwriting

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-W35-Sun-2

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)

Channel	Native caption
Tiktok	We post event recaps before the closing keynote. The trick: pipe stage audio into a live transcript, tag each speaker as a chapter, then search the transcript by keyword to pull clips with timecodes attached. Same-day coverage, real quotes. (AI-assisted edit.)
Instagram	Cut the recap while it's still live. Live transcript of the stage feed. Speakers become chapters. Search by keyword, get timecodes. Posted before the keynote ends. #eventcoverage #videoproduction #livecontent #recap #temerarii
Linkedin	Takeaway for event teams: the slow part of coverage was never the camera, it was the search. Pipe the stage audio into a live transcript and the whole workflow inverts. Tag each speaker as a chapter and the recap writes its own running order. Search the transcript by keyword and the clip timecodes come back attached, so a same-day story is a query rather than a hunt through footage. We have shipped recaps before the closing keynote, quotes intact and on the record. Build the transcript pipe first; everything downstream is a search on it.
X	Event coverage truth: the slow part was the search, not the camera. Live transcript of the stage feed, speakers as chapters, search by keyword to pull clips with timecodes. Recap posted before the closing keynote. temerarii.com
Facebook	Event coverage used to mean a crew on site and weeks of editing. We flipped it: pipe the stage audio into a live transcript, tag each speaker as a chapter, and search the transcript by keyword so clip timecodes come back attached. The result is a same-day recap with real quotes, sometimes posted before the closing keynote starts. See how it works at temerarii.com.
Threads	The slow part of event coverage was never the camera, it was finding the moment. Live transcript of the stage feed, speakers tagged as chapters, search by keyword and the clip timecodes come back. Same-day recap, real quotes, posted before the keynote ends.
Pinterest	Live event video coverage workflow: real-time stage audio transcription, speaker chapter tagging, keyword search to pull clips with timecodes, and same-day recap editing. Evergreen guide to fast event content production and conference recap reels.
Bluesky	Event coverage truth: the slow part was the search. Live transcript of the stage feed, speakers as chapters, keyword search to pull clips with timecodes. Recap posted before the closing keynote. temerarii.com
Youtube	Same-Day Event Coverage: Live Transcripts, Speaker Chapters & Keyword Clips Event coverage used to mean a camera crew and weeks of editing. We invert it. Pipe the stage audio into a live transcript so every quote is searchable in seconds. Tag each speaker as a chapter so the recap writes its own running order. Search the transcript by keyword and clip timecodes come back attached, turning a same-day recap into a query instead of a hunt. We've shipped recaps before the closing keynote, with quotes intact and on the record. More at temerarii.com. #eventcoverage #videoproduction #livecontent

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

#	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.3s	spatial-parallax	icon·ember-fill	♪ bed_in	Old event coverage meant a camera crew, then weeks of editing before anyone saw a clip. on-screen: Event footage sat for weeks
	expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Event footage sat for weeks
2	still pending matches intent shared field signature-3d	hook	6.3–12.6s	kinetic-build	icon·color	♪ node_lock	Now we cut the recap while the event is still happening, not after everyone goes home. on-screen: Cut while it is live
	expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape octaground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Cut while it is live
3	still pending matches intent NumberedList template	teach	12.6–18.5s	kinetic-build	icon·color	♪ node_lock	Pipe the stage audio through a live transcript so every quote is searchable in seconds. on-screen: Transcribe the stage feed
	expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Transcribe the stage feedcurate items, nodes
4	still pending matches intent ComparisonTable template	proof	18.5–24.8s	receipts-count	icon·color	♪ node_lock	We tag each speaker as a chapter, so the recap reel writes its own running order. on-screen: Speaker names become chapters
	expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Speaker names become chapterscurate colA, colB, rows, statsLabels
5	still pending matches intent BuildLog template	diff	24.8–31.1s	crossfade-8f	icon·color	♪ node_lock	This is not a highlight dump, it is a same-day story built from the transcript itself. on-screen: Not just a highlight dump
	expected on screen: white ground · a BuildLog panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape octaground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Not just a highlight dumpcurate codeLines, lines
6	still pending matches intent ChecklistCard template	teach	31.1–36.300000000000004s	kinetic-build	icon·color	♪ node_lock	Search the transcript for your keyword, and the clip timecodes come back attached. on-screen: Pull quotes by keyword
	expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Pull quotes by keywordcurate items, nodes
7	still pending matches intent KpiGrid template	proof	36.3–41.5s	receipts-count	icon·color	♪ node_lock	We have shipped recaps before the closing keynote even started, with quotes intact. on-screen: Posted before the closing keynote
	expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape octaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Posted before the closing keynotecurate kpis, statsLabels
8	still pending matches intent BlueprintGrid template	step	41.5–47.4s	kinetic-build	icon·color	♪ node_lock	Step one is the transcript pipe, because everything downstream is just a query on it. on-screen: Run the transcript pipe first
	expected on screen: white ground · a BlueprintGrid panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id BlueprintGridvisual pipelineshape octaground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Run the transcript pipe firstcurate rows, stages, steps
9	still pending matches intent shared field signature-3d	resolve	47.4–53.699999999999996s	coalescence	icon·ember-fill	♪ bed_out	Same-day, on the record, every quote real. That is how The Big T-M covers a room. on-screen: Same-day, on the record
	expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Same-day, on the record

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

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