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

Copy the published post text

Field Notes
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-field-notes-W25-Sat
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
TiktokField note: a flow with 27 nodes for one job. The old way wired up trigger, parse, branch, format, and send across a dozen boxes. One model call with two tools does the same job. Find your most fragile flow and delete a box this week. (AI-assisted)
InstagramField note: 27 nodes for one job. The old way wired trigger, parse, branch, format, send across a dozen boxes. Now: one model call, two tools, full job. Find your most fragile flow. Delete a box this week. #automation #aiagents #buildinpublic #aimarketing #thebigtm
LinkedinField note: we found a flow with twenty-seven nodes doing one job. The old way wired up trigger, parse, branch, format, and send across a dozen separate boxes. Every box was one more thing that could break. The new shape: one model call with two tools handles the whole job. Fewer parts, fewer failures. A move for this week: find your most fragile flow and ask whether one model with two tools could replace it. Usually the answer is yes.
XField note: 27 nodes for one job. The old way wired trigger, parse, branch, format, send across a dozen boxes. One model call with two tools does the same job. Find your most fragile flow and delete a box this week. temerarii.xyz/build
FacebookField note: we found a flow with twenty-seven nodes doing one job. The old way wired up trigger, parse, branch, format, and send across a dozen boxes, each one a chance to break. Now one model call with two tools does the whole job. Find your most fragile flow and ask if one model with two tools could replace it. Usually yes.
ThreadsField note: 27 nodes for one job. The old way wired trigger, parse, branch, format, send across a dozen boxes. One model call with two tools does the same job. Find your most fragile flow and ask: could one model with two tools do this? Usually yes.
PinterestField note on simplifying automation: a flow with 27 nodes replaced by one model call with two tools. The old way wired trigger, parse, branch, format, and send across a dozen fragile boxes. How to collapse a brittle automation into a single model call, from The Big T-M.
BlueskyField note: 27 nodes for one job. The old way wired trigger, parse, branch, format, send across a dozen boxes. One model call with two tools does the same job. Find your most fragile flow and delete a box this week.
YoutubeTitle: 27 Nodes, One Job | Field Notes | The Big T-M A field note from the bench: we found an automation with twenty-seven nodes doing one job. The old way wired up trigger, parse, branch, format, and send across a dozen separate boxes, each a chance to break. One model call with two tools does the same job. The move: find your most fragile flow and ask whether one model with two tools could replace it. Usually yes. Method-only, no hype.

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

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
first render · fix pending
shared field
signature-3ddead_air
hook0–5.0skinetic-buildicon·liquid-chrome♪ node_lock
Field note: we found a flow with twenty-seven nodes wired up to do one small job.
on-screen: 27 nodes for one job
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→27 nodes for one job
2s2
matches intent
NumberedList
template
teach5.0–11.0skinetic-buildicon·white-knockout♪ node_lock
The old way wired up trigger, parse, branch, format, send, across a dozen boxes.
on-screen: One model call, full job
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→One model call, full jobcurate items, nodes
3s3
matches intent
DiffCard
template
diff11.0–17.1scrossfade-8ficon·liquid-chrome♪ node_lock
Find your most fragile flow and ask: could one model with two tools do this. Usually yes.
on-screen: Delete a box this week
expected on screen: red ground · a DiffCard panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual codeshape dodecaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Delete a box this weekcurate codeLines, lines
4s4
first render · fix pending
ProcessFlow
templatedead_airgeneric_scene
proof17.1–22.1sreceipts-counticon·white-knockout♪ node_lock
Field Notes
expected on screen: red ground · a ProcessFlow panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowvisual receiptsshape dodecaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Field Notescurate statsLabels, steps
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve22.1–27.1scoalescenceicon·white-knockout♪ bed_out
Field Notes
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Field Notes

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