Traditional Media — social-W36-Mon-1 — Temerarii Media Back Office

post social-W36-Mon-1kind threadweek W36date 2026-09-07campaign thread · Monpillar brandbeat Monasset videoduration 48.4sground 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-W36-Mon-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 · 48.4s · 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.0s	spatial-parallax	icon·white-knockout	♪ bed_in	Screenwriting used to start with a blank page that stared right back. on-screen: The blank script page was the enemy
	expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape icosaground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→The blank script page was the enemy
2	still pending matches intent shared field signature-3d	hook	5.0–10.2s	kinetic-build	icon·white-knockout	♪ node_lock	You could burn a whole day just to limp through the first act. on-screen: You burned a day on act one
	expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape icosaground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→You burned a day on act one
3	still pending matches intent NumberedList template	teach	10.2–16.5s	kinetic-build	icon·liquid-chrome	♪ node_lock	Now we hand a model the logline and ask it to draft the beat sheet first. on-screen: Now we draft the beats with AI
	expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape icosaground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Now we draft the beats with AIcurate items, nodes
4	still pending matches intent ComparisonTable template	proof	16.5–22.0s	receipts-count	icon·white-knockout	♪ node_lock	It maps the beats, then you write dialogue over a skeleton that already works. on-screen: Beats first, dialogue second
	expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape icosaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Beats first, dialogue secondcurate colA, colB, rows, statsLabels
5	still pending matches intent TerminalRun template	diff	22.0–27.0s	crossfade-8f	icon·liquid-chrome	♪ node_lock	Left alone, the model writes dialogue that is flat and weirdly polite. on-screen: AI alone writes flat dialogue
	expected on screen: red ground · a TerminalRun panel over a dimmed Signal Field · Signum leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id TerminalRunvisual codeshape icosaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→AI alone writes flat dialoguecurate codeLines
6	still pending matches intent ChecklistCard template	teach	27.0–32.5s	kinetic-build	icon·white-knockout	♪ node_lock	So you feed it each character's want and the line they would never say. on-screen: Give each character a clear want
	expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape icosaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Give each character a clear wantcurate items, nodes
7	still pending matches intent KpiGrid template	proof	32.5–37.5s	receipts-count	icon·liquid-chrome	♪ node_lock	Now the scene has friction, because every character wants something real. on-screen: The scene fights for a reason
	expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape icosaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→The scene fights for a reasoncurate kpis, statsLabels
8	still pending matches intent AnnotatedDiagram template	step	37.5–43.4s	kinetic-build	icon·white-knockout	♪ node_lock	Try it: ask for a beat sheet from your logline, then write the lines yourself. on-screen: Draft the beat sheet, then fill in
	expected on screen: red ground · a AnnotatedDiagram panel over a dimmed Signal Field · Signum leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id AnnotatedDiagramvisual pipelineshape icosaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Draft the beat sheet, then fill incurate callouts, stages, steps
9	still pending matches intent shared field signature-3d	resolve	43.4–48.4s	coalescence	icon·white-knockout	♪ bed_out	The blank page is beaten before your coffee even goes cold. on-screen: Blank page beaten before coffee
	expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Blank page beaten before coffee

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)

tiktokBeat the blank page before your coffee goes cold. Here is the move (AI-assisted): hand the model your logline, get a beat sheet first, then write dialogue over a skeleton that already works. Feed each character a clear want so the scene actually fights. #screenwriting #writingtips #aitools

instagramBeat the blank page. Hand AI your logline. Get the beat sheet first. Give each character a want. Now the scene fights for a reason. #screenwriting #writerslife #filmmaking #aitools #storytelling

linkedinScreenwriting used to start with a blank page that stared back. Now we hand a model the logline for a beat sheet, then write dialogue over a structure that already works. The takeaway: feed each character a clear want and the line they would never say, and the scene earns its friction. Receipts over hype.

xScreenwriting move: hand AI your logline, get a beat sheet first, then write dialogue over it. Give each character a want so the scene actually fights. temerarii.com

facebookScreenwriting used to start with a blank page that stared back. Now we hand a model the logline, get the beat sheet first, then write dialogue over a skeleton that works. Give each character a clear want and the scene fights for a reason. See it at temerarii.com.

threadsBeat the blank page: hand AI your logline, get a beat sheet first, then write the dialogue yourself. Feed each character a want so the scene actually has friction.

pinterestAI screenwriting workflow: how to beat the blank page. Hand the model your logline for a beat sheet, then write dialogue over the structure. Give each character a clear want for real friction. Evergreen guide to script writing, story structure, and screenwriting tools.

blueskyScreenwriting move: hand AI your logline, get a beat sheet first, then write dialogue over it. Give each character a want so the scene fights. temerarii.com

youtubeAI Screenwriting: Beat The Blank Page With A Beat Sheet First Screenwriting used to start with a blank page that stared back, and you could burn a day on act one. The real method: hand a model your logline and ask for the beat sheet first, then write dialogue over a skeleton that already works. Models write flat, polite dialogue alone, so feed each character a clear want and the line they would never say. Now the scene earns its friction. More at temerarii.com.

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

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