Back Office · office.temerarii.xyz
One published post, granular — the Social for W23 Thu, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW23-Thu-social-5kindSocialweekW23dayThudate2026-06-11campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

Minus the Hype
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

thread-minus-the-hype-W23-Thu
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
TiktokEvery automation pitch ends with set it and forget it. Then it breaks at 2am. What works: every run logs to a sheet and pings you the second it fails. (AI-assisted)
InstagramMinus the hype: set it and forget it is how automations break quietly. What actually works, every run writes to a sheet, and it pings you the moment something fails. Build the alarm before you trust the robot.
LinkedinMinus the hype: every automation pitch ends with set it and forget it, and then it breaks at the worst time. What actually works is boring, every run logs to a sheet and pings you the moment it fails. The real cost is building that monitor first, before you ever trust the bot.
XSet it and forget it is how automations break quietly. What works: every run logs to a sheet and pings you the second it fails. Build the alarm first.
FacebookMinus the hype: set it and forget it is how automations break at 2am. What works, every run logs to a sheet and alerts you the moment it fails.
ThreadsSet it and forget it is how automations break quietly. What works: every run logs to a sheet and pings you when it fails. Build the alarm first.
PinterestAutomation best practice: never set it and forget it, log every run to a sheet and send an alert the moment it fails.
BlueskySet it and forget it is how automations break quietly. What works: every run logs to a sheet and pings you when it fails. Build the alarm first.
YoutubeMinus the hype: every automation pitch ends with set it and forget it, and then it breaks at the worst possible time. What actually works is unglamorous, every run logs to a sheet and pings you the moment it fails. Build that monitor first, before you ever trust the bot.

Composition layer × scene 5 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
hook0–8.1skinetic-buildicon·liquid-chrome♪ node_lock
Set it and forget it is the favorite lie in automation. Forgotten bots fail in silence, usually on a weekend.
on-screen: Forgotten bots fail in silence
expected on screen: black ground · icosa hero in the shared Signal Field · Signum leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape icosaground blacktreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→Forgotten bots fail in silence
2s2
matches intent
TerminalRun
template
diff8.1–17.299999999999997scrossfade-8ficon·ember-fill♪ node_lock
What survives is boring. Every run writes a row, and a separate check yells when the rows stop.
on-screen: Log every run. Watch the log.
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Signum leads · code · crossfade-8f · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual codeshape icosaground blacktreatment ember-fillmotion crossfade-8fpower morphinstrument morph→Log every run. Watch the log.curate codeLines
3s3
matches intent
NumberedList
template
teach17.3–22.3skinetic-buildicon·wireframe♪ node_lock
The price is order. You build the alarm before you trust the robot.
on-screen: Alarm first. Trust second.
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Signum leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape icosaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Alarm first. Trust second.curate items, nodes
4s4
matches intent
StatScoreboard
template
proof22.3–27.8sreceipts-counticon·white-knockout♪ node_lock
We learned this the dull way. Our checks run before every single publish.
on-screen: Checks run before every publish
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape icosaground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Checks run before every publishcurate pillar, stats, statsLabels
5s5
matches intent
shared field
signature-3d
resolve27.8–34.0scoalescenceicon·liquid-chrome♪ bed_out
The hype says forget it. The Big T-M says watch it. Watchers win.
on-screen: Watchers win
expected on screen: black ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground blacktreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Watchers win

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