Checklist the per-video bar — engine/sim
83.4/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-build-log-W41-Wed good|bad)⚠ 6 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 6 scenes · 31.5s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  matches intent shared field signature-3d | open | 0–5.9s | spatial-parallax | icon·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 | |||||||
| 2 |  matches intent CodeWindow template | build | 5.9–10.9s | type-on | icon·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 | |||||||
| 3 |  matches intent BuildLog template | diff | 10.9–16.1s | crossfade-8f | icon·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 | |||||||
| 4 |  matches intent PipelineMap template | step | 16.1–21.5s | kinetic-build | icon·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 | |||||||
| 5 |  first render · fix pending KpiGrid templatedead_airgeneric_scene | proof | 21.5–26.5s | receipts-count | icon·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 | |||||||
| 6 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 26.5–31.5s | coalescence | icon·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 | |||||||
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, 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.