SMS — topic-perf-sms — Temerarii Media Back Office

post topic-perf-smskind topicweek —date —campaign performance-pillarpillar performancebeat —asset videoduration 62.1sground blackscenes 9

Checklist the per-video bar — engine/sim

98.5/100

plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness

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

⚠ 1 flag(s) — not yet ship-ready: copy_generic · 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 · 62.1s · 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.7s	spatial-parallax	icon·ember-fill	♪ —	SMS. The most personal channel you own, which is exactly why most brands ruin it. Let us not. on-screen: SMS
	expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→three-mark
2	still pending matches intent KpiGrid template	legacy	6.7–13.2s	crossfade-8f	icon·wireframe	♪ —	The old way was buy a list and blast everyone the same coupon. Fast unsubscribe, slow trust. on-screen: Old way: blast everyone
	expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · crossfade-8f · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id KpiGridshape dodecaground blacktreatment wireframemotion crossfade-8fpower morphinstrument decay→three-symboliccurate kpis
3	still pending matches intent NumberedList template	teach	13.2–21.1s	kinetic-build	icon·wireframe	♪ —	Step one, collect explicit opt-in. SMS is consent-first by law and by manners, so you keep proof of every yes. on-screen: Step 1: get real consent
	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→html-in-canvas-panelcurate items, nodes
4	still pending matches intent ChecklistCard template	teach	21.1–27.8s	kinetic-build	icon·wireframe	♪ —	Step two, give each message exactly one job, one link, one ask. A text is not a newsletter. on-screen: Step 2: one job per text
	expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5	still pending matches intent LegacyCard template	teach	27.8–35.6s	kinetic-build	icon·wireframe	♪ —	Step three, fire texts off behavior, an abandoned cart, a shipped order, not off a calendar nobody cares about. on-screen: Step 3: trigger on behavior
	expected on screen: black ground · a LegacyCard panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id LegacyCardvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes
6	still pending matches intent CodeWindow template	teach	35.6–42.800000000000004s	kinetic-build	icon·wireframe	♪ —	Step four, segment tightly so the message is obviously for them. Generic texts feel like spam because they are. on-screen: Step 4: segment small
	expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual node-graphshape dodecaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate codeLines, nodes, windowTitle
7	still pending matches intent StatScoreboard template	proof	42.8–48.0s	receipts-count	icon·wireframe	♪ —	That is the core: consent, one ask, behavior triggers, real segments. on-screen: Receipts, in the open
	expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate pillar, stats, statsLabels
8	still pending matches intent shared field signature-3d	futurist	48.0–55.5s	spatial-parallax	icon·wireframe	♪ —	What is next is the system drafting the triggered message from the event itself, so the cart-abandon text writes itself, on brand. on-screen: Next: it writes the trigger
	expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · spatial-parallax · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldshape dodecaground blacktreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
9	still pending matches intent shared field signature-3d	resolve	55.5–62.1s	coalescence	icon·ember-fill	♪ swell	SMS that people actually want, because you earned the number. The build is at temerarii dot com. on-screen: temerarii.com
	expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment ember-fillmotion 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)

tiktokSMS is the most personal channel you own, which is exactly why most brands ruin it. (AI-assisted) The method: collect explicit opt-in, SMS is consent-first by law and by manners, so keep proof of every yes. Give each text exactly one job, one link, one ask. A text is not a newsletter. Fire on behavior, an abandoned cart, a shipped order, not a calendar nobody cares about. Segment tightly so the message is obviously for them. Do one thing: rewrite one text down to a single ask and send it on a real trigger.

instagramSMS is the most personal channel you own. Most brands ruin it. The method: Get explicit opt-in, keep proof of every yes One job per text: one link, one ask Fire on behavior, not the calendar Segment tight, so it feels meant for them Generic texts feel like spam because they are. #smsmarketing #retention #crm #aimarketing #temerarii

linkedinSMS is the most personal channel you own, which is exactly why most brands ruin it. Here is the core, given away: 1. Collect explicit opt-in. SMS is consent-first by law and by manners, so keep proof of every yes. 2. Give each message exactly one job: one link, one ask. A text is not a newsletter. 3. Fire texts off behavior, an abandoned cart or a shipped order, not a calendar nobody cares about. 4. Segment tightly so the message is obviously for them. Generic texts feel like spam because they are. The takeaway: stop blasting one coupon to a bought list. Earn the number, then send on real triggers. What is coming: the system drafting the triggered message from the event itself, on brand, so the cart-abandon text writes itself. This week: rewrite one text down to a single ask and fire it on a real behavior trigger.

xSMS is the most personal channel you own, which is why most brands ruin it. Get explicit opt-in, keep proof. One job per text: one link, one ask. Fire on behavior, not the calendar. Segment tight. Generic texts feel like spam because they are. temerarii.com

facebookSMS is the most personal channel you own, which is exactly why most brands ruin it. The core method: collect explicit opt-in and keep proof of every yes, because SMS is consent-first by law and by manners. Give each text one job, one link, one ask. Fire on behavior, an abandoned cart or a shipped order, not a calendar nobody cares about. Segment tightly so the message is obviously for them. This week: rewrite one text down to a single ask and send it on a real trigger. Full build at temerarii.com.

threadsSMS is the most personal channel you own, which is exactly why most brands ruin it. Get explicit opt-in, keep proof of every yes. One job per text: one link, one ask. Fire on behavior, not the calendar. Segment tight so it feels meant for them. Generic texts feel like spam because they are.

pinterestSMS marketing method that people actually want: collect explicit opt-in and keep proof, give each text one job and one ask, trigger on behavior like cart abandons, and segment tightly. A give-it-away guide to consent-first text marketing that earns the number instead of buying it.

blueskySMS is the most personal channel you own, which is why most brands ruin it. Get explicit opt-in, keep proof. One job per text: one link, one ask. Fire on behavior, not the calendar. Segment tight. Generic texts feel like spam because they are.

youtubeSMS People Actually Want: Real Consent, One Ask Per Text, Behavior Triggers, Tight Segments SMS is the most personal channel you own, which is exactly why most brands ruin it. Here is the core method, given away. The steps: 1. Collect explicit opt-in. SMS is consent-first by law and by manners, so keep proof of every yes. 2. Give each message exactly one job: one link, one ask. A text is not a newsletter. 3. Fire texts off behavior, an abandoned cart or a shipped order, not a calendar nobody cares about. 4. Segment tightly so the message is obviously for them. Generic texts feel like spam because they are. What is coming: the system drafting the triggered message from the event itself, on brand, so the cart-abandon text writes itself. Your one next step: rewrite one text down to a single ask and fire it on a real behavior trigger. The full build is at temerarii.com. Method over hype. Receipts over claims.

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

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