Checklist the per-video bar — engine/sim
77.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-receipts-W50-Fri 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 5 scenes · 25.1s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  matches intent StatScoreboard template | stat | 0–5.1s | receipts-count | icon·liquid-chrome | ♪ node_lock | Two public sites, the dot com and the dot xyz, both fed from one content source. We write it once, in one place. on-screen: 2 sites. 1 source. |
expected on screen: red ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→2 sites. 1 source.curate pillar, stats, statsLabels | |||||||
| 2 |  matches intent ComparisonTable template | proof | 5.1–10.1s | receipts-count | icon·white-knockout | ♪ node_lock | Keeping parallel sites used to mean copying every change twice and hoping the two stayed in sync. on-screen: One source, two skins. |
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→One source, two skins.curate colA, colB, rows, statsLabels | |||||||
| 3 |  matches intent DiffCard template | diff | 10.1–15.1s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | Now it is one source, many destinations. We edit the source once and both sites update on their own. on-screen: Single source. |
expected on screen: red ground · a DiffCard panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id DiffCardvisual codeshape boxground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Single source.curate codeLines, lines | |||||||
| 4 |  first render · fix pending CheatSheet templatedead_airgeneric_scene | step | 15.1–20.1s | kinetic-build | icon·white-knockout | ♪ node_lock | Receipts |
expected on screen: red ground · a CheatSheet panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id CheatSheetvisual pipelineshape boxground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Receiptscurate points, stages, steps, uses | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 20.1–25.1s | coalescence | icon·liquid-chrome | ♪ bed_out | Receipts |
expected on screen: red ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Receipts | |||||||
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)
tiktokReceipts: two public sites, dot com and dot xyz, both fed from one content source. Keeping parallel sites used to mean duplicating everything. One source, two skins. The web of the future is one source, many destinations. (AI-assisted)
instagramReceipts.
2 sites. 1 source.
Dot com and dot xyz, both fed from the same content.
Keeping parallel sites used to mean copying everything twice.
Now: one source, two skins.
One source, many destinations.
#contentops #webdev #buildinpublic #automation #thebigtm
linkedinReceipts from our own build: we run two public sites, the dot com and the dot xyz, both fed from one content source.
Keeping parallel sites used to mean duplicating every change twice and hoping they stayed in sync. Now it is one source with two skins.
The takeaway: write once, publish many. One source, many destinations beats maintaining copies by hand every time.
xReceipts: 2 public sites, dot com and dot xyz, both fed from 1 content source. Parallel sites used to mean copying everything twice. Now: one source, two skins. Write once, publish many. temerarii.xyz
facebookReceipts from our own build: two public sites, the dot com and the dot xyz, both fed from one content source.
Keeping parallel sites used to mean copying everything twice. Now it is one source with two skins, so a change shows up in both places at once.
Write once, publish many.
threadsReceipts.
2 sites. 1 source.
Dot com and dot xyz, both fed from the same content.
Keeping parallel sites used to mean copying everything twice. Now it is one source, two skins.
Write once, publish many.
pinterestReceipts: run two websites from one content source. We feed both our dot com and dot xyz from a single source instead of duplicating everything by hand. One source, two skins, write once and publish to many destinations. A cleaner way to run parallel sites.
blueskyReceipts: 2 public sites, dot com and dot xyz, both fed from 1 content source. Parallel sites used to mean copying everything twice. Now: one source, two skins. Write once, publish many.
youtubeTitle: Receipts: Two Websites, One Content Source (Write Once, Publish Many)
We run two public sites, the dot com and the dot xyz, and both are fed from one content source. Keeping parallel sites used to mean duplicating every change twice and hoping they stayed in sync. Now it is one source with two skins, so a single edit shows up in both places. Write once, publish many. More method at temerarii.xyz