Back Office · office.temerarii.xyz
One published post, granular — the Social for W36 Mon, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW36-Mon-social-1kindSocialweekW36dayMondate2026-09-07campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

Traditional Media
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-W36-Mon-1
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)

ChannelNative caption
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.

Composition layer × scene 9 scenes · this post's OWN storyboard (distinct per asset)

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–5.0sspatial-parallaxicon·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
2s2
matches intent
shared field
signature-3d
hook5.0–10.2skinetic-buildicon·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
3s3
matches intent
NumberedList
template
teach10.2–16.5skinetic-buildicon·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
4s4
matches intent
ComparisonTable
template
proof16.5–22.0sreceipts-counticon·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
5s5
matches intent
TerminalRun
template
diff22.0–27.0scrossfade-8ficon·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
6s6
matches intent
ChecklistCard
template
teach27.0–32.5skinetic-buildicon·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
7s7
matches intent
KpiGrid
template
proof32.5–37.5sreceipts-counticon·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
8s8
matches intent
AnnotatedDiagram
template
step37.5–43.4skinetic-buildicon·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
9s9
matches intent
shared field
signature-3d
resolve43.4–48.4scoalescenceicon·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

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