Back Office · office.temerarii.xyz
One published post, granular — the Social for W42 Fri, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW42-Fri-social-5kindSocialweekW42dayFridate2026-10-23campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

Receipts
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-receipts-W42-Fri
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
TiktokFrom a finished build to a live site with one deploy command. No dashboard clicking. The old way was manual: log in to a hosting panel, drag the files, hope it cached right. Now shipping is one line. (AI-assisted)
InstagramReceipt: zero to live in one command. No dashboard clicking. No dragging files into a panel. One deploy line builds it. The same line pushes it live. Script the deploy. #buildinpublic #devops #automation #builtnotbought #ship
LinkedinReceipt: from a finished build to a live site with one deploy command. No dashboard clicking. The old way was manual: log in to a hosting panel, drag the files, and hope it cached right. Now the deploy command builds it and pushes it live in a few seconds. The takeaway: script your deploy. Once shipping is one line, you ship more often and break less. This is how we run our own releases.
XReceipt: finished build to live site in one deploy command. No dashboard clicking, no dragging files into a panel. Script the deploy. How:
FacebookReceipt of the week: we go from a finished build to a live site with one deploy command. No dashboard clicking. The old way was manual: log in to a hosting panel, drag the files, and hope it cached right. The fix is one line. Try scripting your next deploy instead of clicking through a panel.
ThreadsReceipt: from finished build to live site in one deploy command. No dashboard clicking. The old ritual was manual: log in, drag files, hope it cached right. Now shipping is one line. Script the deploy and you ship more often.
PinterestHow to ship a website with one command: script your deploy instead of dragging files through a hosting panel. Deploy automation and CLI shipping method for faster, cleaner releases.
BlueskyReceipt: finished build to live site in one deploy command. The old way was manual, log in, drag files, hope it cached. Now shipping is one line. Script the deploy.
YoutubeTitle: Ship a Site With One Command (Stop Dragging Files) Receipt of the week: we go from a finished build to a live site with one deploy command, no dashboard clicking. The old way was manual: log in to a hosting panel, drag the files, and hope it cached right. Now the deploy command builds and pushes live in seconds. This short shows the move so you can script your own deploy. (AI-assisted)

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
StatScoreboard
template
stat0–5.0sreceipts-counticon·wireframe♪ node_lock
From a finished build to a live site with one deploy command. No dashboard clicking.
on-screen: 0 to live. One command.
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→0 to live. One command.curate pillar, stats, statsLabels
2s2
matches intent
ComparisonTable
template
proof5.0–10.0sreceipts-counticon·wireframe♪ node_lock
The old way was manual: log in to a hosting panel, drag the files, and hope it cached right.
on-screen: CLI ships it.
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→CLI ships it.curate colA, colB, rows, statsLabels
3s3
first render · fix pending
BuildLog
templatedead_air
diff10.0–15.0scrossfade-8ficon·wireframe♪ node_lock
Now shipping is one line: the deploy command builds it and pushes it live in a few seconds.
on-screen: Script the deploy.
expected on screen: white ground · a BuildLog panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual codeshape boxground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Script the deploy.curate codeLines, lines
4s4
first render · fix pending
NodeGraphCard
templatedead_airgeneric_scene
step15.0–20.0skinetic-buildicon·wireframe♪ node_lock
Receipts
expected on screen: white ground · a NodeGraphCard panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual pipelineshape boxground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Receiptscurate hub, nodes, stages, steps
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve20.0–25.0scoalescenceicon·color♪ bed_out
Receipts
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→Receipts

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