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-W44-Wedkind threadweek W44date 2026-11-04campaign thread · Wedpillar brandbeat Wedasset videoduration 33.2sground whitescenes 6

Checklist the per-video bar — engine/sim

85.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review thread-build-log-W44-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 · 33.2s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–8.0sspatial-parallaxicon·color♪ bed_in
Week twenty-two. We shipped automated GIF previews this week, a short looping clip from every video, under one megabyte.
on-screen: Shipped: GIFs from real video
expected on screen: white ground · icosa hero in the shared Signal Field · Signum leads · node-graph · spatial-parallax · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape icosaground whitetreatment colormotion spatial-parallaxpower summoninstrument summon→Shipped: GIFs from real video
2s2
matches intent
StackTrace
template		build8.0–13.0stype-onicon·color♪ node_lock
The old way was hand-exporting each GIF and praying about the file size.
on-screen: Old way: export GIFs by hand
expected on screen: white ground · a StackTrace panel over a dimmed Signal Field · Signum leads · code · type-on · icon·color logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual codeshape icosaground whitetreatment colormotion type-onpower summoninstrument draw-on→Old way: export GIFs by handcurate codeLines, errMsg, errType, fix, frames
3s3
matches intent
CodeWindow
template		diff13.0–18.2scrossfade-8ficon·color♪ node_lock
It broke on size and color. The first GIFs were four megabytes and banded badly.
on-screen: What broke: 4MB and ugly
expected on screen: white ground · a CodeWindow panel over a dimmed Signal Field · Signum leads · code · crossfade-8f · icon·color logo · caption bottom-left
spec (the prompt): comp_id CodeWindowvisual codeshape icosaground whitetreatment colormotion crossfade-8fpower morphinstrument morph→What broke: 4MB and uglycurate codeLines, windowTitle
4s4
matches intent
ProcessFlow
template		step18.2–23.2skinetic-buildicon·color♪ node_lock
Now every video has a tiny preview. Next, we make them play on hover.
on-screen: Next: hover-to-play on the site
expected on screen: white ground · a ProcessFlow panel over a dimmed Signal Field · Signum leads · pipeline · kinetic-build · icon·color logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowvisual pipelineshape icosaground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Next: hover-to-play on the sitecurate stages, steps
5s5
first render · fix pending
ComparisonTable
templatedead_airgeneric_scene		proof23.2–28.2sreceipts-counticon·color♪ node_lock
Build Log
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Signum leads · receipts · receipts-count · icon·color logo · caption bottom-left
spec (the prompt): comp_id ComparisonTablevisual receiptsshape icosaground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Build Logcurate colA, colB, rows, statsLabels
6s6
first render · fix pending
shared field
signature-3ddead_airgeneric_scene		resolve28.2–33.2scoalescenceicon·color♪ bed_out
Build Log
expected on screen: white ground · icosa hero in the shared Signal Field · Signum leads · coalescence · coalescence · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape icosaground whitetreatment colormotion 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)

tiktokBuild log: we shipped automated GIF previews this week. A short looping clip from every video, under one megabyte. The old way was hand-exporting each one and praying about file size. (AI-assisted)
instagramBuild log. Shipped: automated GIF previews. A short loop from every video. Under one megabyte. Old way: hand-export and pray about size. Next: play on hover. #buildinpublic #devlog #automation #video #ffmpeg
linkedinBuild log for the week: we shipped automated GIF previews, a short looping clip pulled from every video, each under one megabyte. The old way was hand-exporting each GIF and hoping about the file size. The first pass broke on size and color: four megabytes and bad banding. Now every video gets a tiny preview automatically. Next up, we make them play on hover. Small thing, but it compounds across hundreds of assets.
xBuild log: shipped automated GIF previews. A loop from every video, under 1MB. Old way was hand-exporting and praying about file size. Next: play on hover. office.temerarii.xyz
facebookThis week's build log: we shipped automated GIF previews, a short loop from every video, all under one megabyte. The old way was hand-exporting each one and praying about the file size. Next, we make them play on hover. Following along with the build? Drop a question below.
threadsBuild log. Shipped automated GIF previews this week. A short loop from every video, under one megabyte. Old way: hand-export each one and pray about size. First pass broke at 4MB with bad banding. Next: play on hover.
pinterestBuild log: how we automated GIF previews from video. A short looping clip from every video, kept under one megabyte. Lessons on file size and color banding, plus next steps for hover-to-play. Video automation and ffmpeg workflow notes.
blueskyBuild log: shipped automated GIF previews. A short loop from every video, under 1MB. Old way was hand-exporting and praying about size. Next: play on hover.
youtubeTitle: Build Log: Automated GIF Previews Under 1MB This week we shipped automated GIF previews, a short looping clip pulled from every video and kept under one megabyte. The old way was hand-exporting each GIF and praying about the file size. The first pass broke on size and color: four megabytes with bad banding. Now every video gets a tiny preview automatically. Next, we make them play on hover.

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

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view