Social — W23 Thu — Temerarii Media Back Office

postW23-Thu-social-4kindSocialweekW23dayThudate2026-06-11campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

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-W23-Thu-4

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	Your newsletter is a monologue. Let what a reader CLICKS pick their next email, so each person walks a path their own clicks built. Write a list of one. (AI-assisted) #emailmarketing #newsletter
Instagram	You talked weekly, they never replied. Let the click pick the next email. Write as if the list had one person. #emailmarketing #newsletter #email #marketing #personalization
Linkedin	Email newsletters used to be a monologue shouted at a silent crowd: you talked weekly and never learned what any single reader wanted. The shift is to let what a reader clicks decide the very next email they get, so each person walks a path their own clicks built, not one you forced. Instead of one path for everyone, let the data branch it, and let AI draft the next message based on what that reader just did, writing as if the list had one person, because to them it does. Start with two simple branches before you build a maze. Email that listens beats email that shouts.
X	Your newsletter is a monologue. Let what a reader clicks pick their next email. temerarii.com
Facebook	Your newsletter talks weekly and never learns what one reader wants. Let what a reader clicks decide their next email, branch the path by behavior, and let AI write as if the list had one person. Start with two branches. Want email that listens? Visit temerarii.com.
Threads	Newsletters used to be a monologue. You talked, they never replied. Let what a reader clicks pick their next email, so each person walks a path their own clicks built. Start with two branches before a maze. Email that listens beats email that shouts.
Pinterest	Email personalization tips: let each reader's clicks decide the next email they receive, branch the journey by behavior instead of sending one path to everyone, use AI to draft the next message based on what they just did, and start with two simple branches. Build behavior-driven newsletter journeys that feel one-to-one.
Bluesky	Your newsletter is a monologue. Let what a reader clicks pick their next email. temerarii.com
Youtube	Turn Your Newsletter Monologue Into A Conversation Newsletters shout at a silent crowd. Let what a reader clicks pick their next email, branch the path by behavior, and write as if the list had one person. Start with two branches. AI-assisted production. Learn personalization at temerarii.com.

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–5.0s	spatial-parallax	icon·white-knockout	♪ bed_in	Email newsletters used to be a monologue shouted at a silent crowd. on-screen: Newsletters were a monologue
	expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Newsletters were a monologue
2	still pending matches intent shared field signature-3d	hook	5.0–10.0s	kinetic-build	icon·ember-fill	♪ node_lock	You talked weekly and never learned what any single reader wanted. on-screen: You talked, they never replied
	expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground blacktreatment ember-fillmotion kinetic-buildpower laser-lockinstrument laser-trace→You talked, they never replied
3	still pending matches intent NumberedList template	teach	10.0–15.7s	kinetic-build	icon·wireframe	♪ node_lock	The move: let what a reader clicks decide the very next email they get. on-screen: Let the click pick the next email
	expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Let the click pick the next emailcurate items, nodes
4	still pending matches intent ComparisonTable template	proof	15.7–20.7s	receipts-count	icon·white-knockout	♪ node_lock	Each reader walks a path their own clicks built, not one you forced. on-screen: Behavior writes the journey
	expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape dodecaground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Behavior writes the journeycurate colA, colB, rows, statsLabels
5	still pending matches intent TerminalRun template	diff	20.7–26.7s	crossfade-8f	icon·liquid-chrome	♪ node_lock	Old way: one path for everyone. We let the data branch the path. on-screen: We don't send one path to all
	expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id TerminalRunvisual codeshape dodecaground blacktreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→We don't send one path to allcurate codeLines
6	still pending matches intent ChecklistCard template	teach	26.7–31.7s	kinetic-build	icon·ember-fill	♪ node_lock	Now AI drafts the next message based on what that reader just did. on-screen: AI drafts the branch on the fly
	expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→AI drafts the branch on the flycurate items, nodes
7	still pending matches intent KpiGrid template	proof	31.7–37.4s	receipts-count	icon·wireframe	♪ node_lock	It writes as if the list had one person, because to them it does. on-screen: It writes a list of one
	expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→It writes a list of onecurate kpis, statsLabels
8	still pending matches intent FlowSchematic template	step	37.4–42.4s	kinetic-build	icon·white-knockout	♪ node_lock	Step: start with two simple branches before you build a maze. on-screen: Map two branches, then grow
	expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id FlowSchematicvisual pipelineshape dodecaground blacktreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Map two branches, then growcurate stages, steps
9	still pending matches intent shared field signature-3d	resolve	42.4–48.6s	coalescence	icon·white-knockout	♪ bed_out	Email that listens beats email that shouts. The Big T-M makes it listen. on-screen: Email that listens back
	expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Email that listens back

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

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