Back Office · office.temerarii.xyz
One asset, all the way in — composition, the wireframe + storyboard, the output format stack, and the template, all read from the SAME content-index record. The expected output matches what /media surfaces for this post.
post thread-build-log-W52-Wedkind threadweek W52date 2026-12-30campaign thread · Wedpillar brandbeat Wedasset videoduration 36.1sground redscenes 6

Checklist the per-video bar — engine/sim

86.1/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-build-log-W52-Wed good|bad)
⚠ 5 flag(s) — not yet ship-ready: low_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template BuildLog
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 6 scenes · 36.1s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
open0–6.6sspatial-parallaxicon·liquid-chrome♪ bed_in
Week thirty. We shipped the last build log of the year, and the whole thing was built in the open, every step.
on-screen: Shipped: 30 weeks, in public
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape icosaground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Shipped: 30 weeks, in public
2s2
matches intent
BuildLog
template
build6.6–14.9stype-onicon·white-knockout♪ node_lock
Studios used to hide their methods behind a curtain. We did the opposite, publishing the exact AI and API steps every single week.
on-screen: Old way: hide how it's made
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Signum leads · code · type-on · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BuildLogvisual codeshape icosaground redtreatment white-knockoutmotion type-onpower summoninstrument draw-on→Old way: hide how it's madecurate codeLines, lines
3s3
matches intent
DiffCard
template
diff14.9–19.9scrossfade-8ficon·liquid-chrome♪ node_lock
The thing that almost broke us was the instinct to keep the good parts secret.
on-screen: What broke: thinking we'd hold back
expected on screen: red ground · a DiffCard panel over a dimmed Signal Field · Signum leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id DiffCardvisual codeshape icosaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→What broke: thinking we'd hold backcurate codeLines, lines
4s4
matches intent
BlueprintGrid
template
step19.9–26.099999999999998skinetic-buildicon·white-knockout♪ node_lock
What's now possible: a studio anyone can study and copy. Next year, come build alongside us.
on-screen: Next: build with us, in 2027
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Signum leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual pipelineshape icosaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Next: build with us, in 2027curate rows, stages, steps
5s5
first render · fix pending
ComparisonTable
templatedead_airgeneric_scene
proof26.1–31.1sreceipts-counticon·liquid-chrome♪ node_lock
Build Log
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape icosaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Build Logcurate colA, colB, rows, statsLabels
6s6
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve31.1–36.1scoalescenceicon·liquid-chrome♪ bed_out
Build Log
expected on screen: red ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Build Log

Format stack 3 aspects · same scenes[], re-cropped

9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 9 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky

Social captions supplemental published copy · per channel (comp_id level)

tiktokWeek thirty. We shipped the last build log of the year, all of it built in the open. Studios used to hide their methods. We published the exact AI and API steps every week. Next year, come build alongside us. (AI-assisted)
instagramWeek 30. Last build log of the year. Built in the open, every step. Studios hide their methods. We published the exact AI and API steps every single week. Next year: build with us. #buildinpublic #buildlog #aitools #automation #studio
linkedinWeek thirty. We shipped the last build log of the year, and the whole thing was built in the open, every step. Studios usually hide their methods behind a curtain. We did the opposite: publishing the exact AI and API steps every single week. The thing that almost broke us was the instinct to keep the good parts secret. What that makes possible: a studio anyone can study and copy. Next year, come build alongside us.
xWeek 30. The last build log of the year, all built in the open. Studios hide their methods. We published the exact AI and API steps every week. Next year, build with us. temerarii.xyz
facebookWeek thirty, and we shipped the last build log of the year. The whole thing was built in the open, every step. Studios used to hide their methods behind a curtain. We did the opposite and published the exact AI and API steps every single week. Next year, come build alongside us.
threadsWeek 30. Last build log of the year, built in the open every step. Studios hide their methods. We published the exact AI and API steps every single week. The thing that almost broke us was wanting to keep the good parts secret. Next year, build with us.
pinterestA full year of building a studio in public: 30 weekly build logs publishing the exact AI and API steps, with nothing hidden behind a curtain. Why we shared the method instead of keeping the good parts secret, and how to study and copy the whole approach next year.
blueskyWeek 30. Last build log of the year, built in the open every step. Studios hide their methods. We published the exact AI and API steps every week. Next year, build with us.
youtubeTitle: 30 Weeks of Building a Studio in Public (Year-End Build Log) Week thirty. We shipped the last build log of the year, and the whole thing was built in the open, every step. Studios usually hide their methods behind a curtain. We did the opposite, publishing the exact AI and API steps every single week. The thing that almost broke us was the instinct to keep the good parts secret. What it makes possible: a studio anyone can study and copy. Next year, come build alongside us. (AI-assisted)

Cross-links every lens is a view on this one record