Back Office · office.temerarii.xyz
One published post, granular — the Social for W28 Sun, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW28-Sun-social-3kindSocialweekW28daySundate2026-07-12campaignhub-launchcadence5/day floor × 9 channels

Copy the published post text

Software Development
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-W28-Sun-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
Tiktokthe future of building software (and yes, AI-assisted): you describe the feature in plain words, an agent reads your repo, writes the change, runs the tests. the spec stops being a dead doc and starts being the build. #softwaredev #aitools #coding
InstagramDescribe the feature. Get a running app today. The spec becomes the build. Humans keep the hard calls. #softwaredevelopment #aitools #coding #buildinpublic #tech
LinkedinTakeaway: the spec is becoming the software. Instead of a doc that rots while a team works through a backlog, you write a plain-language description, an agent like Claude Code reads the repo, writes the change, and runs the tests. Keep humans on the hard architectural calls and let the agent handle the typing and wiring. Software is starting to ship at the speed you can describe it.
XThe future of software: you describe the feature in plain words, an agent edits the repo and runs the tests. The spec stops being a dead doc and becomes the build. temerarii.com
FacebookBuilding software used to mean a team, a backlog, and months of waiting. Now you describe a feature in plain words and an agent reads your repo, writes the change, and runs the tests. The spec becomes the build. See how at temerarii.com.
ThreadsThe future of software: describe the feature in plain words, an agent reads your repo, writes the change, runs the tests. The spec stops being a dead doc and becomes the build. Humans keep the hard calls.
PinterestFuture of software development with AI coding agents: plain-language specs that build running apps, agents that edit your repo and run tests, spec-driven development. AI software tools, vibe coding, agentic development workflow, build faster tips.
BlueskyThe future of software: describe the feature in plain words, an agent edits the repo and runs the tests. The spec stops being a dead doc and becomes the build. temerarii.com
YoutubeThe Future Of Software: Your Spec Becomes The Build Building software used to mean a team, a backlog, and months before anyone saw a demo, while the spec rotted in a doc. This short shows where it is going: you describe a feature in plain words, an agent like Claude Code reads your repo, writes the change, and runs the tests. Keep humans on the hard architectural calls and let the agent do the typing and wiring. Software is starting to ship at the speed you can describe it. AI-assisted. More at temerarii.com.

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.9sspatial-parallaxicon·white-knockout♪ bed_in
Building software used to mean a team, a backlog, and months before anyone saw it.
on-screen: Software meant a team and months
expected on screen: red ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Software meant a team and months
2s2
matches intent
shared field
signature-3d
hook5.9–12.5skinetic-buildicon·white-knockout♪ node_lock
The spec rotted in a doc while the world moved on, and the demo came too late.
on-screen: Specs rotted before the demo
expected on screen: red ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Specs rotted before the demo
3s3
matches intent
NumberedList
template
teach12.5–18.8skinetic-buildicon·liquid-chrome♪ node_lock
Now you describe the feature in plain words and get a running app the same day.
on-screen: Describe it, get a running app
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Describe it, get a running appcurate items, nodes
4s4
matches intent
ComparisonTable
template
proof18.8–24.3sreceipts-counticon·white-knockout♪ node_lock
Tools like Claude Code read your repo, write the change, and run the tests.
on-screen: Claude Code edits the real repo
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Claude Code edits the real repocurate colA, colB, rows, statsLabels
5s5
matches intent
DiffCard
template
diff24.3–29.8scrossfade-8ficon·liquid-chrome♪ node_lock
What changed: the plain-language spec became the thing that builds, not a dead doc.
on-screen: Spec is now the source
expected on screen: red ground · a DiffCard panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual codeshape boxground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Spec is now the sourcecurate codeLines, lines
6s6
matches intent
ChecklistCard
template
teach29.8–35.7skinetic-buildicon·white-knockout♪ node_lock
Keep humans on the hard calls, let the agent do the typing and the wiring.
on-screen: Keep humans on the hard calls
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Keep humans on the hard callscurate items, nodes
7s7
matches intent
KpiGrid
template
proof35.7–40.900000000000006sreceipts-counticon·liquid-chrome♪ node_lock
Soon one person describes a tool at breakfast and ships it before lunch.
on-screen: One person ships a real tool
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape boxground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→One person ships a real toolcurate kpis, statsLabels
8s8
matches intent
BlueprintGrid
template
step40.9–46.4skinetic-buildicon·white-knockout♪ node_lock
Your step: write a one-paragraph spec for a tiny internal tool, then build it.
on-screen: Your step: spec one small tool
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual pipelineshape boxground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Your step: spec one small toolcurate rows, stages, steps
9s9
matches intent
shared field
signature-3d
resolve46.4–51.6scoalescenceicon·white-knockout♪ bed_out
The future is software that ships at the speed you can describe it.
on-screen: Ideas ship at the speed of words
expected on screen: red ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Ideas ship at the speed of words

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