Back Office · office.temerarii.xyz
One published post, granular — the Social for W23 Fri, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW23-Fri-social-5kindSocialweekW23dayFridate2026-06-12campaignlongform-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-W23-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
TiktokThe receipt: one brief became every social post for the week, scheduled across every channel. One file fans out to all of them. (AI-assisted)
InstagramReceipts. One brief became every social post for the week, lined up across every channel. The trick is plain: one file holds the plan and fans out to each platform, so the receipt is the schedule itself.
LinkedinReceipts over rhetoric: one brief became every social post for the week, scheduled across every channel. The method is plain, one file holds the plan and fans out to each platform automatically. The receipt is the schedule itself, not a slide about it.
XReceipt: one brief became every social post for the week, scheduled across every channel. One file holds the plan and fans out to all of them.
FacebookReceipts: one brief turned into every social post for the week, scheduled across every channel, because one file holds the plan and fans out to each platform.
ThreadsReceipt: one brief became every social post for the week, across every channel. One file holds the plan and fans out to all of them.
PinterestContent automation receipt: turn one brief into a full week of scheduled social posts by fanning a single plan file out to every channel.
BlueskyReceipt: one brief became every social post for the week, scheduled across every channel. One file holds the plan and fans out to all of them.
YoutubeReceipts over rhetoric: one brief became every social post for the week, scheduled across every channel. The method is plain, a single file holds the whole plan and fans it out to each platform, so the proof is the schedule itself.

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
KpiGrid
template
stat0–12.6sreceipts-counticon·liquid-chrome♪ node_lock
Receipt time. One idea went out on nine channels this week. Same brand, same story, nine cuts. No agency. No big team. Just the method.
on-screen: One idea. Nine channels.
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape octaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→One idea. Nine channels.curate kpis, statsLabels
2s2
matches intent
RankList
template
proof12.6–18.3sreceipts-counticon·white-knockout♪ node_lock
You can check this. The office site is public. Every post for the week is on it.
on-screen: The office is public. Go look.
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape octaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→The office is public. Go look.curate rows, statsLabels
3s3
matches intent
TerminalRun
template
diff18.3–27.6scrossfade-8ficon·liquid-chrome♪ node_lock
Here is how. The plan lives in one file. A script reads it and cuts the idea for each channel. That is the whole trick.
on-screen: One file runs the week
expected on screen: red ground · a TerminalRun panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual codeshape octaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→One file runs the weekcurate codeLines
4s4
matches intent
SchematicCard
template
step27.6–33.300000000000004skinetic-buildicon·white-knockout♪ node_lock
Want this? Start with one idea. Cut it three ways. Then post all three.
on-screen: Cut one idea three ways
expected on screen: red ground · a SchematicCard panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual pipelineshape octaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Cut one idea three wayscurate nodes, stages, steps
5s5
matches intent
shared field
signature-3d
resolve33.3–39.099999999999994scoalescenceicon·white-knockout♪ bed_out
No claims without proof here. The Big T-M shows its work every Friday.
on-screen: Proof every Friday
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Proof every Friday

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