Checklist the per-video bar — engine/sim
73.1/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-receipts-W37-Fri good|bad)⚠ 7 flag(s) — not yet ship-ready: copy_generictoo_complexlow_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.9s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  matches intent KpiGrid template | stat | 0–5.9s | receipts-count | icon·wireframe | ♪ node_lock | Sixty-four content topics, weighted by importance, planned from a single source file. on-screen: 64 topics. 1 file. |
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→64 topics. 1 file.curate kpis, statsLabels | |||||||
| 2 |  matches intent RankList template | proof | 5.9–10.9s | receipts-count | icon·wireframe | ♪ node_lock | Editorial calendars used to live in one head. We moved ours into a plain text file anyone can read and edit. on-screen: YAML drives the plan. |
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape dodecaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→YAML drives the plan.curate rows, statsLabels | |||||||
| 3 |  matches intent TerminalRun template | diff | 10.9–15.9s | crossfade-8f | icon·wireframe | ♪ node_lock | The calendar of the future is computed from that file, not guessed, so adding a topic edits one line. on-screen: Weight the topics. |
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id TerminalRunvisual codeshape dodecaground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Weight the topics.curate codeLines | |||||||
| 4 |  first render · fix pending ListCard templatedead_airgeneric_scene | step | 15.9–20.9s | kinetic-build | icon·wireframe | ♪ node_lock | Receipts |
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Mensor leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ListCardvisual pipelineshape dodecaground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Receiptscurate items, stages, steps | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 20.9–25.9s | coalescence | icon·white-knockout | ♪ bed_out | Receipts |
expected on screen: black ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground blacktreatment white-knockoutmotion 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)
tiktokReceipt: 64 content topics, weighted by importance, planned from one source file. Editorial calendars used to live in someone head. Ours lives in a plain text file anyone can read and edit. The calendar of the future is computed, not guessed. Want it? Steal the pattern. (AI-assisted)
instagramReceipt.
64 content topics.
1 source file.
Editorial calendars used to live in someone head.
Ours lives in a plain text file anyone can read and edit. Weight the topics by importance, and the plan builds itself.
The calendar of the future is computed, not guessed.
#buildinpublic #contentstrategy #editorialcalendar #marketingops #yaml
linkedinReceipt: 64 content topics, weighted by importance, all planned from a single source file.
Editorial calendars used to live in someone head, or scattered across a dozen spreadsheets. Ours lives in one plain text file that anyone can read and edit.
The move: list every topic, give each a weight, and let the plan compute itself from those weights. Adding a topic edits one line, not a whole calendar.
The calendar of the future is computed, not guessed in a meeting. That is the receipt, and the pattern is yours to copy.
xReceipt: 64 content topics, weighted by importance, planned from one source file.
Editorial calendars used to live in someone head. Ours is a plain text file you can read and edit.
The calendar of the future is computed, not guessed.
facebookReceipt: 64 content topics, weighted by importance, all planned from a single source file.
Editorial calendars used to live in someone head. Ours lives in one plain text file that anyone can read and edit. You list the topics, give each a weight, and the plan computes itself.
The calendar of the future is computed, not guessed in a meeting. Steal the pattern.
threadsReceipt: 64 content topics, weighted by importance, planned from one source file.
Editorial calendars used to live in someone head. Ours lives in a plain text file anyone can read and edit. List the topics, weight them, the plan builds itself.
Computed, not guessed.
pinterestReceipts: planning 64 content topics from a single source file, weighted by importance. Instead of an editorial calendar living in someone head or a dozen spreadsheets, keep it in one plain text file anyone can read and edit. List topics, assign weights, and let the plan compute itself. A computed content calendar pattern you can copy.
blueskyReceipt: 64 content topics, weighted, from one source file.
Editorial calendars used to live in someone head. Ours is a plain text file you can read and edit. Computed, not guessed.
youtubeTitle: Receipts: 64 Content Topics Planned From One Plain Text File
Here is the receipt: 64 content topics, weighted by importance, all planned from a single source file. Editorial calendars used to live in someone head or scattered across spreadsheets. Ours lives in one plain text file anyone can read and edit. List the topics, give each a weight, and the plan computes itself, so adding a topic edits one line. The calendar of the future is computed, not guessed. Pattern is yours to copy. The Big T-M, temerarii.xyz.