It actually works — the open, running machine (proof on screen) — social-W34-Wed-1

post social-W34-Wed-1kind threadweek W34date 2026-08-26campaign thread · Wedpillar it_devbeat Wedasset videoduration 49.6sground redscenes 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-W34-Wed-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 · 49.6s · 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–5.9s	spatial-parallax	icon·liquid-chrome	♪ bed_in	Email used to mean one big blast to everyone and a quiet prayer for opens. on-screen: Email used to be one blast
	expected on screen: red ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Email used to be one blast
2	still pending matches intent shared field signature-3d	hook	5.9–11.4s	kinetic-build	icon·white-knockout	♪ node_lock	A message written for everyone reads like it was written for absolutely no one. on-screen: One message for all fits none
	expected on screen: red ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→One message for all fits none
3	still pending matches intent NumberedList template	teach	11.4–17.3s	kinetic-build	icon·liquid-chrome	♪ node_lock	The method: split your list by what people actually did, not by who they are. on-screen: Segment by what people did
	expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape boxground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Segment by what people didcurate items, nodes
4	still pending matches intent RankList template	proof	17.3–23.200000000000003s	receipts-count	icon·white-knockout	♪ node_lock	The person who clicked twice wants a different note than the one who never opened. on-screen: Behavior beats demographics
	expected on screen: red ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape boxground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Behavior beats demographicscurate rows, statsLabels
5	still pending matches intent JsonDiff template	diff	23.2–28.2s	crossfade-8f	icon·liquid-chrome	♪ node_lock	Sending more email rarely helps; sending the right email almost always does. on-screen: Relevance gets the reply
	expected on screen: red ground · a JsonDiff panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id JsonDiffvisual codeshape boxground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Relevance gets the replycurate codeLines, fileName, lines
6	still pending matches intent ChecklistCard template	teach	28.2–33.4s	kinetic-build	icon·white-knockout	♪ node_lock	Now AI drafts a tailored version for each segment from one short outline. on-screen: AI writes a version per segment
	expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→AI writes a version per segmentcurate items, nodes
7	still pending matches intent StatScoreboard template	proof	33.4–38.9s	receipts-count	icon·liquid-chrome	♪ node_lock	We sent fewer emails to each person and got more honest replies in return. on-screen: Replies rose, unsubscribes fell
	expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Replies rose, unsubscribes fellcurate pillar, stats, statsLabels
8	still pending matches intent StepFlow template	step	38.9–44.4s	kinetic-build	icon·white-knockout	♪ node_lock	Your step: split your next send into clicked and ignored, and write to each. on-screen: Split clicked vs ignored
	expected on screen: red ground · a StepFlow panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id StepFlowvisual pipelineshape boxground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Split clicked vs ignoredcurate stages, steps
9	still pending matches intent shared field signature-3d	resolve	44.4–49.6s	coalescence	icon·liquid-chrome	♪ bed_out	Soon each note will assemble itself around what that one reader last did. on-screen: Soon each note writes itself
	expected on screen: red ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Soon each note writes itself

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)

tiktokAn email written for everyone reads like it's for no one. The move: segment by what people DID, not who they are, clicked twice vs never opened get different notes. (AI-assisted) AI drafts a version per segment from one outline. Right email beats more email.

instagramEmail, old way: one blast to all. A note for everyone fits no one. Segment by behavior, not demographics. AI writes a version per segment. #emailmarketing #segmentation #crm #marketingtips #temerarii

linkedinEmail used to mean one big blast to everyone and a prayer for opens, but a message written for everyone reads like it was written for no one. The method that fixes it: segment your list by what people actually did, not by who they are. The person who clicked twice wants a different note than the one who never opened. What's new: AI drafts a tailored version per segment from one short outline, so you send fewer emails per person and get more honest replies. Takeaway: relevance, not volume, earns the reply.

xAn email for everyone reads like it's for no one. Segment by what people did, not who they are. AI drafts a version per segment from one outline. Right email beats more email. temerarii.xyz

facebookEmail used to mean one big blast to everyone and a prayer for opens, but a message for everyone reads like it's for no one. The move: segment by what people actually did, not who they are. The person who clicked twice wants a different note than the one who never opened. Now AI drafts a tailored version per segment from one short outline. We sent fewer emails and got more replies. Want our segmentation starter? Just ask.

threadsAn email written for everyone reads like it's for no one. Segment by what people DID, not who they are. Clicked twice vs never opened = different notes. AI drafts a version per segment from one outline. Right email beats more email.

pinterestEmail marketing that gets replies: segment your list by behavior, not demographics. The person who clicked twice needs a different message than the one who never opened. Use AI to draft a tailored version for each segment from one outline. Email marketing, list segmentation, CRM strategy, email automation.

blueskyAn email for everyone reads like it's for no one. Segment by what people did, not who they are. AI drafts a version per segment. Right email beats more email. temerarii.xyz

youtubeEmail Marketing: Segment by Behavior, Not Demographics Email used to mean one big blast to everyone and a quiet prayer for opens, but a message written for everyone reads like it was written for no one. The method that fixes it: split your list by what people actually did, not by who they are. The person who clicked twice wants a different note than the one who never opened. What's new: AI drafts a tailored version for each segment from one short outline, so you send fewer emails per person and get more honest replies. Soon each note will assemble itself around what that reader last did. Your step: split your next send into clicked and ignored, and write to each. Relevance, not volume, earns the reply. AI-assisted production. More 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