Cyber Security — social-W35-Sun-3 — Temerarii Media Back Office

post social-W35-Sun-3kind threadweek W35date 2026-08-30campaign thread · Sunpillar it_devbeat Sunasset videoduration 58.9sground 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-W35-Sun-3 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 · 58.9s · 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·wireframe	♪ bed_in	Most brand systems live in a PDF nobody opens, so every post drifts a little further off. on-screen: Brand guide in a PDF nobody opens
	expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment wireframemotion spatial-parallaxpower summoninstrument summon→Brand guide in a PDF nobody opens
2	still pending matches intent shared field signature-3d	hook	6.6–13.6s	kinetic-build	icon·color	♪ node_lock	Now we make the rules a file the tools read, not a document people are meant to remember. on-screen: Make the rules a file
	expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Make the rules a file
3	still pending matches intent NumberedList template	teach	13.6–19.5s	kinetic-build	icon·color	♪ node_lock	Put your colors, fonts, and spacing into design tokens, plain values any app can pull. on-screen: Colors and fonts become tokens
	expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape boxground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Colors and fonts become tokenscurate items, nodes
4	still pending matches intent RankList template	proof	19.5–26.1s	receipts-count	icon·color	♪ node_lock	That one token file feeds the site, the deck, and the social template at the same time. on-screen: One token file feeds everything
	expected on screen: white ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape boxground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→One token file feeds everythingcurate rows, statsLabels
5	still pending matches intent DiffCard template	diff	26.1–33.1s	crossfade-8f	icon·color	♪ node_lock	This is not brand by vibes, it is one source of truth that the whole team draws from. on-screen: Not vibes, a single source
	expected on screen: white ground · a DiffCard panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id DiffCardvisual codeshape boxground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Not vibes, a single sourcecurate codeLines, lines
6	still pending matches intent ChecklistCard template	teach	33.1–39.0s	kinetic-build	icon·color	♪ node_lock	Add a check that flags any color outside the tokens before the post ever ships. on-screen: A linter for off-brand color
	expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→A linter for off-brand colorcurate items, nodes
7	still pending matches intent StatScoreboard template	proof	39.0–46.0s	receipts-count	icon·color	♪ node_lock	When a stray hex slips in, the check catches it at the door instead of in the feed. on-screen: Drift caught at the door
	expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Drift caught at the doorcurate pillar, stats, statsLabels
8	still pending matches intent ListCard template	step	46.0–52.6s	kinetic-build	icon·color	♪ node_lock	Step one for your team is the token file, then point every tool at that one place. on-screen: Start with the token file
	expected on screen: white ground · a ListCard panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ListCardvisual pipelineshape boxground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Start with the token filecurate items, stages, steps
9	still pending matches intent shared field signature-3d	resolve	52.6–58.9s	coalescence	icon·wireframe	♪ bed_out	Consistency you can actually run, not hope for. That is the system at The Big T-M. on-screen: Consistency you can run
	expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Consistency you can run

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)

tiktokYour brand guide is a PDF nobody opens. Make it a file the tools read instead: put colors, fonts, and spacing into design tokens, feed one token file into your site, deck, and social template, then add a check that flags any off-token color before posting. (AI-assisted edit.)

instagramBrand by vibes is how you drift. Colors and fonts become tokens. One file feeds site, deck, social. A check flags off-brand color. Drift caught at the door. #brandsystems #designtokens #brandidentity #designops #temerarii

linkedinTakeaway for anyone training a team on brand: stop shipping the guide as a PDF. Encode your colors, fonts, and spacing as design tokens, plain values your tools can read. Feed that one token file into the website, the deck, and the social template so they all draw from a single source of truth. Then add a simple check that flags any color outside the token set before a post ships, so drift is caught at the door instead of discovered in the feed. Consistency you can run beats consistency you hope for.

xBrand systems truth: your guide is a PDF nobody opens. Make it a file the tools read. Colors and fonts as design tokens, one file feeding site + deck + social, plus a check that flags off-token color before you post. temerarii.com

facebookMost brand systems live in a PDF nobody opens, so every post drifts. The fix for your team: turn colors, fonts, and spacing into design tokens, feed that one file into your site, deck, and social template, and add a check that flags any off-brand color before it ships. Consistency you can actually run. Learn the setup at temerarii.com.

threadsYour brand guide is a PDF nobody opens. Make it a file the tools read. Colors and fonts as design tokens, one file feeding site + deck + social template, plus a check that flags off-brand color before you post. Drift caught at the door, not in the feed.

pinterestBrand system setup for teams: convert colors, fonts, and spacing into design tokens, feed one token file into website, deck, and social templates, and add an off-token color check to prevent brand drift. Evergreen design-ops and brand consistency guide.

blueskyBrand truth: your guide is a PDF nobody opens. Make it a file the tools read. Design tokens for color and type, one file feeding site + deck + social, plus a check that flags off-brand color before posting. temerarii.com

youtubeBrand Systems as Code: Design Tokens, One Source of Truth & Drift Checks Most brand systems live in a PDF nobody opens, so every post drifts a little. Here's the method we teach teams: encode your colors, fonts, and spacing as design tokens, plain values any app can read. Feed that one token file into the website, deck, and social template so they share a single source of truth. Then add a check that flags any color outside the tokens before a post ships, catching drift at the door. Consistency you can run beats consistency you hope for. More at temerarii.com. #brandsystems #designtokens #designops

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

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