Checklist the per-video bar — engine/sim
84.9/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W29-Tue-2 good|bad)⚠ 4 flag(s) — not yet ship-ready: copy_generictoo_complexdup_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 · 65.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 shared field signature-3d | open | 0–7.3s | spatial-parallax | icon·white-knockout | ♪ bed_in | An event used to run on a clipboard, a guest list on paper, and one person praying nobody no-shows. on-screen: Events used to run on paper |
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→Events used to run on paper | |||||||
| 2 |  matches intent shared field signature-3d | hook | 7.3–14.6s | kinetic-build | icon·white-knockout | ♪ node_lock | Day-of chaos was treated as normal, as if a hundred moving parts could only ever be herded by panic. on-screen: The day-of chaos was the norm |
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→The day-of chaos was the norm | |||||||
| 3 |  matches intent NumberedList template | teach | 14.6–21.9s | kinetic-build | icon·liquid-chrome | ♪ node_lock | We write the run-of-show as one shared sheet: every cue, who owns it, and the exact minute it happens. on-screen: Write the run-of-show as one sheet |
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→Write the run-of-show as one sheetcurate items, nodes | |||||||
| 4 |  matches intent ComparisonTable template | proof | 21.9–29.2s | receipts-count | icon·white-knockout | ♪ node_lock | One row per cue, one name beside each, so no moment of the day belongs to nobody at all. on-screen: One row per cue, one owner each |
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→One row per cue, one owner eachcurate colA, colB, rows, statsLabels | |||||||
| 5 |  matches intent BuildLog template | diff | 29.2–37.3s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | The Big T-M rehearses the sheet, not just the room, because the plan fails on paper before it fails on stage. on-screen: We rehearse the sheet, not just the |
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape tetraground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→We rehearse the sheet, not just the roomcurate codeLines, lines | |||||||
| 6 |  matches intent ChecklistCard template | teach | 37.3–43.599999999999994s | kinetic-build | icon·white-knockout | ♪ node_lock | Read the run-of-show backward, from teardown to doors, and the missing handoffs jump out at you. on-screen: Read it backward to find the gaps |
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→Read it backward to find the gapscurate items, nodes | |||||||
| 7 |  matches intent KpiGrid template | proof | 43.6–50.9s | receipts-count | icon·liquid-chrome | ♪ node_lock | When one cue slips, the shared sheet shows it live, so the next owner adjusts instead of getting blindsided. on-screen: When a cue slips, everyone sees it |
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→When a cue slips, everyone sees itcurate kpis, statsLabels | |||||||
| 8 |  matches intent BlueprintGrid template | step | 50.9–58.199999999999996s | kinetic-build | icon·white-knockout | ♪ node_lock | Try it: list every cue, give each one owner and one minute, then read the whole thing backward once. on-screen: Do this |
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id BlueprintGridvisual pipelineshape tetraground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Do this: one cue, one owner, one minutecurate rows, stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 58.2–65.9s | coalescence | icon·white-knockout | ♪ bed_out | A calm event is not luck or charm. It is a boring sheet that everyone read before the doors opened. on-screen: Calm is just a good plan |
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→Calm is just a good plan | |||||||
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)
tiktokDay-of event chaos isn't normal, it's a planning gap (AI-assisted method). Write the run-of-show as ONE shared sheet: one row per cue, one owner each, one exact minute. Then read it BACKWARD from teardown to doors and the missing handoffs jump out. Calm = a boring sheet everyone read. #eventplanning #events #ops
instagramDay-of chaos isn't normal.
Run-of-show = one shared sheet.
One cue, one owner, one minute.
Read it backward to find the gaps.
Calm is just a good plan.
#eventplanning #events #production #ops #strategy
linkedinEvent coordination without the day-of panic. The old way ran on a paper guest list and one person hoping nobody no-shows. We write the run-of-show as one shared sheet: every cue, one owner per row, one exact minute. Then we rehearse the sheet, not just the room, and read it backward from teardown to doors, which makes the missing handoffs jump out. When a cue slips, everyone sees it live and adjusts. A calm event is a boring sheet everyone read before the doors opened.
xDay-of event chaos isn't normal, it's a planning gap. Write the run-of-show as ONE shared sheet: one cue, one owner, one minute. Read it BACKWARD from teardown to doors and the missing handoffs jump out.
facebookAn event used to run on a clipboard and one person praying nobody no-shows. Day-of chaos got treated as normal. We write the run-of-show as one shared sheet: one row per cue, one owner each, one exact minute, then read it backward from teardown to doors to find the missing handoffs. A calm event is just a boring sheet everyone read. See how in the video.
threadsDay-of event chaos isn't normal, it's a planning gap. Write the run-of-show as ONE shared sheet: one cue, one owner, one minute. Read it backward from teardown to doors and the missing handoffs jump out. Calm = a boring sheet everyone read.
pinterestEvent planning method: run of show template, event timeline, cue sheet, day-of coordination, event production checklist, assign owners, rehearse the plan, avoid event chaos. How a boring shared sheet turns a hundred moving parts into a calm day.
blueskyDay-of event chaos isn't normal, it's a planning gap. Write the run-of-show as ONE shared sheet: one cue, one owner, one minute. Read it backward to find the missing handoffs.
youtubeEvent Coordination: One Sheet, One Owner per Cue, Read It Backward
An event used to run on a clipboard and one person praying nobody no-shows, with day-of chaos treated as normal. We write the run-of-show as one shared sheet: every cue, one owner per row, one exact minute. We rehearse the sheet, not just the room, and read it backward from teardown to doors so the missing handoffs jump out. When a cue slips, everyone sees it live and adjusts. A calm event is a boring sheet everyone read before the doors opened. AI-assisted, human-judged.