Back Office · office.temerarii.xyz
One published post, granular — the Social for W33 Sun, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW33-Sun-social-1kindSocialweekW33daySundate2026-08-16campaigncase-studiescadence5/day floor × 9 channels

Copy the published post text

Custom apps (runnable tools)
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-W33-Sun-1
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
TiktokStop building chatbots that just talk. (AI-assisted) Here's how to ship a runnable tool instead: one form, one model call, one clean answer on screen. Inputs locked by a schema so it can't break in front of a client. A tool gets used daily. A tip gets forgotten by lunch.
InstagramDon't ship advice. Ship a tool people can run. Form in. Model call. Answer out. Schema locks the input so it never breaks. #customtools #aiapps #buildinpublic #automation #aitools
LinkedinMost AI deliverables are a deck and a PDF nobody opens twice. The better move: wrap the model call behind one button, give it a typed input form, and ship it as a small web app. The client clicks once, your code runs the prompt, a clean answer lands. Constrain inputs with a schema so bad data gets rejected before it reaches the model. A runnable tool gets used daily. A tip gets forgotten by lunch. That's the difference between an idea and an asset.
XStop shipping chatbots that talk. Wrap the model call behind one button. Typed form in, answer out, schema locks the input so it can't break. A tool gets used daily. A tip's gone by lunch. temerarii.com
FacebookMost AI work ends as a PDF nobody reopens. Build a runnable tool instead: a form, one model call, a clean answer on screen, with a schema that blocks bad input. People use tools. They forget tips. See how we build them at temerarii.com
ThreadsStop shipping chatbots that just talk. Wrap the model call behind one button. Typed form in, clean answer out. Schema locks the input so it can't break in front of a client. A tool gets used daily. A tip's forgotten by lunch.
PinterestHow to build a custom AI app: turn a chatbot into a runnable tool with a typed input form, one model call, and a schema that blocks bad input. Custom AI tools, no-deck AI deliverables, web app from a prompt, AI automation for clients.
BlueskyStop shipping chatbots that talk. Wrap the model call behind one button: form in, answer out, schema locks the input. A tool gets used daily, a tip's gone by lunch. temerarii.com
YoutubeCustom AI Apps: Turn a Chatbot Into a Runnable Tool Most AI deliverables die as a PDF nobody reopens. In this short we show the real move: wrap a model call behind one button, give it a typed input form, and ship it as a small web app. Add a schema so bad input gets rejected before it ever reaches the model. The result is a tool clients actually run every day instead of advice they forget by lunch. Chapters: the old PDF problem, the one-button pattern, locking inputs with a schema, and the three-step build (form, model call, render). #customtools #aiapps #automation

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·wireframe♪ bed_in
Most chatbots talk. The Big T-M builds you a tool that actually does the job.
on-screen: A chat that does the work
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→A chat that does the work
2s2
matches intent
shared field
signature-3d		hook5.9–12.2skinetic-buildicon·wireframe♪ node_lock
Old way, you got a slide deck and a how-to PDF that nobody ever opened again.
on-screen: The old way: a PDF nobody runs
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→The old way: a PDF nobody runs
3s3
matches intent
NumberedList
template		teach12.2–21.299999999999997skinetic-buildicon·wireframe♪ node_lock
Here is the move: wrap a model call behind one button, give it a typed form, and ship it as a small web app.
on-screen: Wrap a model in one button
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Wrap a model in one buttoncurate items, nodes
4s4
matches intent
RankList
template		proof21.3–28.3sreceipts-counticon·wireframe♪ node_lock
Your client clicks once, your code runs the prompt, and a clean answer lands in front of them.
on-screen: User clicks, code runs, answer ships
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→User clicks, code runs, answer shipscurate rows, statsLabels
5s5
matches intent
DiffCard
template		diff28.3–33.8scrossfade-8ficon·wireframe♪ node_lock
A tip gets forgotten by lunch. A runnable tool gets used every single day.
on-screen: A tool beats a tip
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual codeshape boxground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→A tool beats a tipcurate codeLines, lines
6s6
matches intent
ChecklistCard
template		teach33.8–41.5skinetic-buildicon·wireframe♪ node_lock
Now constrain the inputs with a schema, so the user can only feed it what the model can safely handle.
on-screen: Lock inputs so it can't break
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Lock inputs so it can't breakcurate items, nodes
7s7
matches intent
StatScoreboard
template		proof41.5–48.5sreceipts-counticon·wireframe♪ node_lock
Bad input gets rejected up front, so the thing never melts down in front of a paying customer.
on-screen: Wrong input gets caught early
expected on screen: black 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 blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Wrong input gets caught earlycurate pillar, stats, statsLabels
8s8
matches intent
BlueprintGrid
template		step48.5–56.6skinetic-buildicon·wireframe♪ node_lock
Three steps: build the form, route it to one model call, render the result on screen. That is the whole app.
on-screen: Step: form, model call, render
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual pipelineshape boxground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Step: form, model call, rendercurate rows, stages, steps
9s9
matches intent
shared field
signature-3d		resolve56.6–62.9scoalescenceicon·wireframe♪ bed_out
Stop handing people advice. Hand them a working tool, and watch how fast they trust you.
on-screen: Hand over a tool, not a talk
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Hand over a tool, not a talk

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

→ Day (full output set) → Source video → Media (audience preview) → Calendar→ Storyboard hub