Back Office · office.temerarii.xyz
One published post, granular — the Social for W34 Wed, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW34-Wed-social-3kindSocialweekW34dayWeddate2026-08-26campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

Strategic Partnerships
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-W34-Wed-3
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
TiktokSomeone on your team is copying data between tabs RIGHT NOW. Boring work feels free until you add up the hours. The move: write the trigger, steps, and result on ONE page before automating. (AI-assisted) Then AI wires the tools together. Automate the boring, keep the judgment.
InstagramThe same task, by hand, every day. Manual work feels free. It isn't. Map trigger to steps to result first. AI wires the tools together. #automation #workflow #productivity #aitools #temerarii
LinkedinRight now, someone on your team is copying the same data between tabs again. Boring manual work feels free until you add up the hours it quietly eats. The method that fixes it: write the trigger, the steps, and the result before you automate anything, because mapping the flow first means you automate it once, not three broken times. What's new: AI reads the map and wires the tools together with the logic in between, turning a one-hour morning chore into something that runs before anyone wakes up. Takeaway: automate the boring, keep the human judgment.
XSomeone on your team is copying data between tabs right now. Map the trigger, steps, result on one page first. Then AI wires the tools together. Automate the boring, keep the judgment. temerarii.xyz
FacebookRight now, someone on your team is copying the same data between tabs again. Boring manual work feels free until you add up the hours it eats. The move: write the trigger, steps, and result on one page before you automate anything. Then AI wires the tools together, and a one-hour morning chore runs before anyone wakes up. Automate the boring, keep the judgment. Got a chore worth killing? Tell us.
ThreadsSomeone on your team is copying data between tabs right now. Boring work feels free until you add up the hours. Write the trigger, steps, result on one page first. Then AI wires the tools. Automate the boring, keep the judgment.
PinterestWorkflow automation that actually sticks: write the trigger, the steps, and the result on one page before you automate anything. Map it once so you build it once. Then use AI to wire your tools together. Workflow automation, productivity systems, business automation, AI tools.
BlueskySomeone on your team is copying data between tabs right now. Map the trigger, steps, result first. Then AI wires the tools. Automate the boring, keep the judgment. temerarii.xyz
YoutubeAutomated Workflows: Map It Before You Automate It Right now, someone on your team is copying the same data between tabs again. Boring manual work feels free until you add up the hours it quietly eats. The method that fixes it: write the trigger, the steps, and the result before you automate anything, because mapping the flow first means you automate it once instead of three broken times. What's new: AI reads the map and wires the tools together with the logic in between, turning a one-hour morning chore into something that runs before anyone wakes up. Soon you'll describe the flow in a sentence and watch the wiring build itself. Your step: write trigger, steps, result on one page before you touch any tool. Automate the boring, keep the judgment. AI-assisted production. More at temerarii.xyz

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·liquid-chrome♪ bed_in
Someone, somewhere, is copying the same data between tabs again right now.
on-screen: The same task by hand, daily
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→The same task by hand, daily
2s2
matches intent
shared field
signature-3d
hook5.0–10.5skinetic-buildicon·white-knockout♪ node_lock
Boring manual work feels free until you add up the hours it quietly eats.
on-screen: Manual work hides the real cost
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Manual work hides the real cost
3s3
matches intent
NumberedList
template
teach10.5–16.4skinetic-buildicon·liquid-chrome♪ node_lock
The method: write the trigger, the steps, and the result before you automate a thing.
on-screen: Map the trigger, steps, result
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Map the trigger, steps, resultcurate items, nodes
4s4
matches intent
RankList
template
proof16.4–21.9sreceipts-counticon·white-knockout♪ node_lock
Mapping the flow first meant we automated it once instead of three broken times.
on-screen: Mapped first, automated once
expected on screen: red ground · a RankList panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape tetraground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Mapped first, automated oncecurate rows, statsLabels
5s5
matches intent
CodeWindow
template
diff21.9–27.4scrossfade-8ficon·liquid-chrome♪ node_lock
Automate the boring parts and keep the human judgment where it earns its keep.
on-screen: Automate boring, keep judgment
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape tetraground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Automate boring, keep judgmentcurate codeLines, windowTitle
6s6
matches intent
ChecklistCard
template
teach27.4–33.3skinetic-buildicon·white-knockout♪ node_lock
Now AI reads the map and wires the tools together with the logic in between.
on-screen: AI connects the steps for you
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→AI connects the steps for youcurate items, nodes
7s7
matches intent
StatScoreboard
template
proof33.3–38.8sreceipts-counticon·liquid-chrome♪ node_lock
A chore that ate an hour each morning now runs before anyone wakes up.
on-screen: A daily chore became invisible
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→A daily chore became invisiblecurate pillar, stats, statsLabels
8s8
matches intent
FlowSchematic
template
step38.8–44.3skinetic-buildicon·white-knockout♪ node_lock
Your step: write trigger, steps, result on one page before you touch any tool.
on-screen: Write the flow before the code
expected on screen: red ground · a FlowSchematic panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual pipelineshape tetraground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Write the flow before the codecurate stages, steps
9s9
matches intent
shared field
signature-3d
resolve44.3–50.199999999999996scoalescenceicon·liquid-chrome♪ bed_out
Soon you will describe the flow in a sentence and watch the wiring build itself.
on-screen: Soon you describe it, it builds it
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Soon you describe it, it builds it

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