Checklist the per-video bar — engine/sim
86.6/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W32-Fri-4 good|bad)⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_sequence_across_assetsdup_set_across_assets · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelpending1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
render pending — silent master not yet on disk
expected output: 0/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 9 scenes · 56.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–5.9s | spatial-parallax | icon·white-knockout | ♪ bed_in | Websites used to be built one handmade page at a time, then patched forever after. on-screen: Sites used to be built page by |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Sites used to be built page by page | |||||||
| 2 |  matches intent shared field signature-3d | hook | 5.9–12.5s | kinetic-build | icon·white-knockout | ♪ node_lock | Now we build from reusable parts fed by data, so one fix updates every page at once. on-screen: Now we build from components and data |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Now we build from components and data | |||||||
| 3 |  matches intent NumberedList template | teach | 12.5–18.8s | kinetic-build | icon·liquid-chrome | ♪ node_lock | The move is making one small component, like a card, and reusing it everywhere it fits. on-screen: Make small components, reuse them |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Make small components, reuse themcurate items, nodes | |||||||
| 4 |  matches intent ComparisonTable template | proof | 18.8–24.3s | receipts-count | icon·white-knockout | ♪ node_lock | Change that one component and every page using it updates, no hunting through files. on-screen: Fix the part, fix the whole site |
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape tetraground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Fix the part, fix the whole sitecurate colA, colB, rows, statsLabels | |||||||
| 5 |  matches intent LogStream template | diff | 24.3–30.6s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | Copy-pasted pages rot on their own schedule until your site is a museum of old fixes. on-screen: Copy-pasted pages rot separately |
expected on screen: red ground · a LogStream panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id LogStreamvisual codeshape tetraground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Copy-pasted pages rot separatelycurate codeLines, rows | |||||||
| 6 |  matches intent ChecklistCard template | teach | 30.6–37.2s | kinetic-build | icon·white-knockout | ♪ node_lock | Let AI draft the first version of a component, then you tighten the spacing and the copy. on-screen: Let AI draft the first pass |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Let AI draft the first passcurate items, nodes | |||||||
| 7 |  matches intent KpiGrid template | proof | 37.2–43.5s | receipts-count | icon·liquid-chrome | ♪ node_lock | AI gets you to a rough page fast; your judgment is what makes it actually good. on-screen: AI drafts fast, you make it right |
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→AI drafts fast, you make it rightcurate kpis, statsLabels | |||||||
| 8 |  matches intent NodeGraphCard template | step | 43.5–50.5s | kinetic-build | icon·white-knockout | ♪ node_lock | Build the part, reuse it, let AI draft, you refine, and the site stays clean as it grows. on-screen: Component, reuse, draft, refine |
expected on screen: red ground · a NodeGraphCard panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardvisual pipelineshape tetraground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Component, reuse, draft, refinecurate hub, nodes, stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 50.5–56.4s | coalescence | icon·white-knockout | ♪ bed_out | That is web design that grows without rotting, because nothing is built by hand twice. on-screen: A site that scales without rotting |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→A site that scales without rotting | |||||||
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)
tiktokWeb design that doesn't rot (AI-assisted). Stop building pages one at a time. Build from reusable COMPONENTS — make one card, reuse it everywhere, and fixing that one part updates every page at once. Copy-pasted pages rot on their own schedule until your site is a museum of old fixes. Let AI draft the first version, then YOU tighten the spacing and copy. #webdesign #webdev #frontend
instagramWeb design that doesn't rot.
Build from reusable components.
Fix one part, every page updates.
AI drafts fast, your judgment makes it good.
#webdesign #webdev #frontend #design #buildinpublic
linkedinHow we build websites that don't rot as they grow:
The old way was building one handmade page at a time, then patching each forever. Copy-pasted pages rot on their own schedule until the site is a museum of old fixes.
The shift: build from reusable components fed by data. Make one small component — a card, say — and reuse it everywhere it fits. Change that one component and every page using it updates, with no hunting through files.
Use AI for the first draft of a component, then apply your judgment to the spacing and copy. AI gets you to a rough page fast; taste is what makes it good.
Takeaway: nothing should be built by hand twice.
xWeb design that doesn't rot: build from reusable components. Make one card, reuse it everywhere — fix that one part and every page updates. Let AI draft the first pass, you refine the spacing and copy. temerarii.com
facebookWebsites used to be built one handmade page at a time, then patched forever. Now we build from reusable components fed by data: make one card, reuse it everywhere, and fixing that one part updates every page at once. Copy-pasted pages rot on their own schedule. Let AI draft the first version, then you tighten the spacing and copy. Web design that grows without rotting. Here's how.
threadsWeb design that doesn't rot: build from reusable components. Make one card, reuse it everywhere — fix that one part and every page updates at once. Copy-pasted pages rot on their own schedule. Let AI draft the first pass, then you refine the spacing and copy.
pinterestModern web design explained: how to build sites from reusable components fed by data so one fix updates every page. A guide to component-based design, avoiding copy-paste rot, and using AI for first drafts. Web design and front-end development basics for beginners.
blueskyWeb design that doesn't rot: build from reusable components. Make one card, reuse it everywhere — fix that part, every page updates. Let AI draft the first pass, you refine. temerarii.com
youtubeWeb Design That Doesn't Rot: Components Over Handmade Pages
Websites used to be built one handmade page at a time, then patched forever — and copy-pasted pages rot on their own schedule until the site is a museum of old fixes. This short shows the shift: build from reusable components fed by data. Make one small component, like a card, and reuse it everywhere it fits, so changing that one part updates every page at once. Use AI for the first draft, then apply your judgment to spacing and copy.
More at temerarii.com.