Back Office · office.temerarii.xyz
One published post, granular — the Social for W41 Wed, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW41-Wed-social-5kindSocialweekW41dayWeddate2026-10-14campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

Build Log
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-build-log-W41-Wed
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
TiktokBuild log, week nineteen. We shipped batch rendering: thirty videos from one command overnight. It broke first, one bad job took the rest down. Now jobs run isolated. (AI-assisted)
InstagramBuild log, week nineteen. Shipped: batch video render. Thirty videos, one command, overnight. It broke first. One crash killed the rest. Fix: isolate each job. #buildinpublic #buildlog #automation #videorender #temerarii
LinkedinBuild log, week nineteen. This week we shipped batch rendering: thirty videos from one command overnight. The old way was rendering one video, waiting, then starting the next by hand. It did not work on the first try. One bad job crashed and took the whole run down with it. The fix was to isolate each job so a single failure cannot kill the rest. Now a night of rendering is one command. Next step: render several at once across cores. We post the misses, not just the wins.
XBuild log wk19: shipped batch rendering. 30 videos, one command, overnight. First run died when one bad job took the rest down. Fix: isolate each job. temerarii.xyz
FacebookBuild log, week nineteen. We shipped batch rendering this week, thirty videos from one command overnight instead of one at a time by hand. It broke on the first run when one bad job took the whole batch down, so we isolated each job. Now a night of work is one command. Follow along at temerarii.xyz.
ThreadsBuild log, week nineteen. Shipped batch rendering: thirty videos from one command overnight. It broke first, one crash took the whole run down. Fix was isolating each job. Now a night of work is one command. Next: render several at once across cores.
PinterestBuild log: shipping batch video rendering. How we went from rendering one video at a time by hand to thirty from a single overnight command, why the first run failed when one bad job crashed the batch, and how isolating each job fixed it.
BlueskyBuild log wk19: shipped batch rendering. 30 videos, one command, overnight. First run died when one bad job took the rest down. Fix: isolate each job.
YoutubeTitle: Build Log Week 19: Batch Rendering 30 Videos From One Command This week we shipped batch rendering: thirty videos from one overnight command, instead of rendering one at a time by hand. It broke on the first run when a single bad job crashed and took the whole batch with it. The fix was isolating each job so one failure cannot kill the rest. Next up: rendering several at once across cores.

Composition layer × scene 6 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·ember-fill♪ bed_in
Week nineteen. We shipped batch rendering this week, thirty videos from one command overnight.
on-screen: Shipped: batch video render
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape knotground whitetreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Shipped: batch video render
2s2
matches intent
CodeWindow
template
build5.9–10.9stype-onicon·color♪ node_lock
The old way was rendering one video, waiting, then starting the next by hand.
on-screen: Old way: render one, wait, repeat
expected on screen: white ground · a CodeWindow panel over a dimmed Signal Field · Magister leads · code · type-on · icon·color logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape knotground whitetreatment colormotion type-onpower summoninstrument draw-on→Old way: render one, wait, repeatcurate codeLines, windowTitle
3s3
matches intent
BuildLog
template
diff10.9–16.1scrossfade-8ficon·color♪ node_lock
It broke on a single bad job. One video crashed and took the rest down with it.
on-screen: What broke: one crash killed the run
expected on screen: white ground · a BuildLog panel over a dimmed Signal Field · Magister leads · code · crossfade-8f · icon·color logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual codeshape knotground whitetreatment colormotion crossfade-8fpower morphinstrument morph→What broke: one crash killed the runcurate codeLines, lines
4s4
matches intent
PipelineMap
template
step16.1–21.5skinetic-buildicon·color♪ node_lock
Now a night's work is one command. Next, we render several at once across cores.
on-screen: Next: render in parallel
expected on screen: white ground · a PipelineMap panel over a dimmed Signal Field · Magister leads · pipeline · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id PipelineMapvisual pipelineshape knotground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Next: render in parallelcurate stages, steps
5s5
first render · fix pending
KpiGrid
templatedead_airgeneric_scene
proof21.5–26.5sreceipts-counticon·color♪ node_lock
Build Log
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id KpiGridvisual receiptsshape knotground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Build Logcurate kpis, statsLabels
6s6
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve26.5–31.5scoalescenceicon·ember-fill♪ bed_out
Build Log
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Build Log

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