Checklist the per-video bar — engine/sim
98.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-build-log-W23-Wed good|bad)⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarerendered16:9 Widerendered9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 3/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 6 scenes · 43.4s · 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–11.5s | spatial-parallax | icon·3d-extrude | ♪ bed_in | Build log, launch week. The content engine is live, the office site is public, and the blog shipped its first posts. Here is how it went. on-screen: Launch week: engine, office, blog |
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·3d-extrude logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground whitetreatment 3d-extrudemotion spatial-parallaxpower summoninstrument summon→Launch week: engine, office, blog | |||||||
| 2 |  matches intent StackTrace template | build | 11.5–18.2s | type-on | icon·color | ♪ node_lock | Every asset starts as a row in one plan file. The engine turns each row into scenes. on-screen: One plan file feeds everything |
expected on screen: white ground · a StackTrace panel over a dimmed Signal Field · Nexus leads · code · type-on · icon·color logo · caption bottom-left spec (the prompt): comp_id StackTracevisual codeshape tetraground whitetreatment colormotion type-onpower summoninstrument draw-on→One plan file feeds everythingcurate codeLines, errMsg, errType, fix, frames | |||||||
| 3 |  matches intent CodeWindow template | diff | 18.2–27.0s | crossfade-8f | icon·color | ♪ node_lock | What broke: one renamed prop. Our long videos rendered pure black because a component still expected the old prop name. on-screen: One renamed prop, black video |
expected on screen: white ground · a CodeWindow panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual codeshape tetraground whitetreatment colormotion crossfade-8fpower morphinstrument morph→One renamed prop, black videocurate codeLines, windowTitle | |||||||
| 4 |  matches intent AnnotatedDiagram template | step | 27.0–32.9s | kinetic-build | icon·color | ♪ node_lock | The fix was small, the lesson was not. Now a pixel check runs after every render. on-screen: Pixel check after every render |
expected on screen: white ground · a AnnotatedDiagram panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id AnnotatedDiagramvisual pipelineshape tetraground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Pixel check after every rendercurate callouts, stages, steps | |||||||
| 5 |  matches intent StatScoreboard template | proof | 32.9–37.9s | receipts-count | icon·color | ♪ node_lock | Proof is public. The whole calendar sits on the office site right now. on-screen: The calendar is public |
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape tetraground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→The calendar is publiccurate pillar, stats, statsLabels | |||||||
| 6 |  matches intent shared field signature-3d | resolve | 37.9–43.4s | coalescence | icon·3d-extrude | ♪ bed_out | Same time next Wednesday. We build it, it breaks, we log it here. on-screen: Next entry: Wednesday |
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→Next entry: Wednesday | |||||||
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 one: shipped the whole launch calendar from one file. Then it broke, the fiscal weeks did not match the dates. Fix: anchor everything to one date. (AI-assisted)
instagramBuild log, week one. We shipped the entire launch calendar, every asset planned from one file. It broke when the fiscal week did not match the dates, so we anchored to a single date and it regenerates itself now.
linkedinBuild log, week one: we generated the whole launch calendar from one source file. It broke, the fiscal week did not line up with the calendar dates, so every cell was off. The fix was anchoring to one date; change the topics now and the calendar rebuilds itself.
xBuild log wk1: generated the whole launch calendar from one file. It broke (fiscal week vs dates). Fix: anchor to one date, change topics, calendar regenerates.
facebookWeek-one build log: we built the launch calendar from a single file. It broke when fiscal weeks did not match the dates, fixed by anchoring to one date so it now regenerates itself.
threadsBuild log wk1: whole launch calendar from one file. Broke when fiscal week did not match dates. Fixed by anchoring to one date, now it regenerates itself.
pinterestContent calendar automation build log: generate the whole calendar from one source file, anchor to a single date so it regenerates when topics change.
blueskyBuild log wk1: built the launch calendar from one file, it broke (fiscal week vs dates), fixed by anchoring to one date so it regenerates itself.
youtubeBuild log, week one: we generated the entire launch calendar from a single source file, hit a real bug where the fiscal week did not match the calendar dates, and fixed it by anchoring everything to one date so the calendar now regenerates whenever the topics change.