Back Office · office.temerarii.xyz
One published post, granular — the Social for W27 Wed, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW27-Wed-social-5kindSocialweekW27dayWeddate2026-07-08campaignlongform-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-W27-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
TiktokWeek five. We shipped fully code-rendered video, no timeline, no mouse. A video is now a function we can call. It broke on version drift first. Next: render 30 in one batch. (AI-assisted)
InstagramBuild log, week 5. Shipped: video rendered by code. No timeline. No mouse. What broke: version drift. One update and every render looked different. Next: 30 videos in one batch. #buildinpublic #remotion #codevideo #automation #buildlog
LinkedinBuild log, week five. We shipped fully code-rendered video this week. No timeline, no mouse. The old way was dragging clips on a timeline for hours per edit. What broke first: version drift. One package update and every render looked different, so we pinned every dependency. Now a video is a function we can call. Next, we render thirty of them in one batch.
XWeek 5: we shipped fully code-rendered video. No timeline, no mouse. It broke on version drift until we pinned every package. A video is now a function we call. Next: 30 in one batch.
FacebookBuild log, week five. We shipped fully code-rendered video this week, with no timeline and no mouse. The old way was dragging clips on a timeline for hours per edit. It broke first on version drift, one package update and every render looked different. Now a video is just a function we can call. Next up, we render thirty of them in one batch. Follow along.
ThreadsBuild log, week 5. We shipped fully code-rendered video. No timeline, no mouse. It broke on version drift first: one package update and every render looked different. We pinned everything. Now a video is a function we can call. Next, thirty in one batch.
PinterestHow we render video entirely in code, no timeline editor. Build log week five: fully code-rendered video, no mouse. The trap is version drift, so pin every package. Once a video is a function you can call, you can batch render thirty at once.
BlueskyWeek 5: we shipped fully code-rendered video. No timeline, no mouse. It broke on version drift until we pinned every package. A video is now a function we call. Next: 30 in one batch.
YoutubeTitle: Build Log Week 5: Video Rendered Entirely In Code This week we shipped fully code-rendered video, with no timeline and no mouse. The old way was dragging clips on a timeline for hours per edit. The first thing that broke was version drift: one package update and every render looked different, so we pinned every dependency. Now a video is a function we can call, and next we render thirty of them in one batch.

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–6.1sspatial-parallaxicon·white-knockout♪ bed_in
Week five. We shipped fully code-rendered video this week, no timeline, no mouse.
on-screen: Shipped: video rendered by code
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape dodecaground blacktreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Shipped: video rendered by code
2s2
matches intent
CodeWindow
template
build6.1–11.1stype-onicon·wireframe♪ node_lock
The old way was dragging clips on a timeline for hours per edit, then re-exporting the whole thing for one text change.
on-screen: Old way: drag clips for hours
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Mensor leads · code · type-on · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape dodecaground blacktreatment wireframemotion type-onpower summoninstrument draw-on→Old way: drag clips for hourscurate codeLines, windowTitle
3s3
matches intent
BuildLog
template
diff11.1–16.3scrossfade-8ficon·wireframe♪ node_lock
It broke on version drift. One package update and every render looked different.
on-screen: What broke: every render pinned wrong
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual codeshape dodecaground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→What broke: every render pinned wrongcurate codeLines, lines
4s4
matches intent
NodeGraphCard
template
step16.3–21.9skinetic-buildicon·wireframe♪ node_lock
Now a video is a function we can call. Next, we render thirty of them in one batch.
on-screen: Next: render 30 at once
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual pipelineshape dodecaground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Next: render 30 at oncecurate hub, nodes, stages, steps
5s5
first render · fix pending
StatScoreboard
templatedead_airgeneric_scene
proof21.9–26.9sreceipts-counticon·wireframe♪ node_lock
Build Log
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Build Logcurate pillar, stats, statsLabels
6s6
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve26.9–31.9scoalescenceicon·white-knockout♪ bed_out
Build Log
expected on screen: black 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 blacktreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Build Log

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