Checklist the per-video bar — engine/sim
98.5/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W23-Sun-3 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 9 scenes · 49.5s · 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.0s | spatial-parallax | icon·3d-extrude | ♪ bed_in | Event work used to live in a hundred email threads nobody could read. on-screen: Event planning lived in inboxes |
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→Event planning lived in inboxes | |||||||
| 2 |  matches intent shared field signature-3d | hook | 5.0–10.0s | kinetic-build | icon·color | ♪ node_lock | Two days out, nobody could say who actually confirmed they were coming. on-screen: Who confirmed? Nobody knew |
expected on screen: white ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Who confirmed? Nobody knew | |||||||
| 3 |  matches intent NumberedList template | teach | 10.0–16.0s | kinetic-build | icon·color | ♪ node_lock | The move: one shared calendar is the boss, and every tool writes to it. on-screen: Make one calendar the boss |
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Make one calendar the bosscurate items, nodes | |||||||
| 4 |  matches intent ComparisonTable template | proof | 16.0–21.0s | receipts-count | icon·color | ♪ node_lock | One source of truth means no two speakers booked in the same room. on-screen: One source, zero double-books |
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape tetraground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→One source, zero double-bookscurate colA, colB, rows, statsLabels | |||||||
| 5 |  matches intent StackTrace template | diff | 21.0–27.5s | crossfade-8f | icon·color | ♪ node_lock | Old way: a meeting to ask who is doing what. We let the data answer. on-screen: We retire the status meeting |
expected on screen: white ground · a StackTrace panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id StackTracevisual codeshape tetraground whitetreatment colormotion crossfade-8fpower morphinstrument morph→We retire the status meetingcurate codeLines, errMsg, errType, fix, frames | |||||||
| 6 |  matches intent ChecklistCard template | teach | 27.5–32.5s | kinetic-build | icon·color | ♪ node_lock | Now AI reads the thread and drafts the follow-up to each vendor for you. on-screen: AI drafts every follow-up |
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→AI drafts every follow-upcurate items, nodes | |||||||
| 7 |  matches intent KpiGrid template | proof | 32.5–38.1s | receipts-count | icon·color | ♪ node_lock | You wake up to replies sorted into confirmed, maybe, and chase-again. on-screen: Replies sorted before coffee |
expected on screen: white ground · a KpiGrid panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape tetraground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Replies sorted before coffeecurate kpis, statsLabels | |||||||
| 8 |  matches intent BlueprintGrid template | step | 38.1–43.300000000000004s | kinetic-build | icon·color | ♪ node_lock | Step: set a rule that nudges any vendor who goes quiet past a day. on-screen: Auto-nudge the quiet vendors |
expected on screen: white ground · a BlueprintGrid panel over a dimmed Signal Field · Nexus leads · pipeline · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id BlueprintGridvisual pipelineshape tetraground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Auto-nudge the quiet vendorscurate rows, stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 43.3–49.5s | coalescence | icon·3d-extrude | ♪ bed_out | A calm room beats a loud inbox. The Big T-M runs the boring part. on-screen: Calm rooms beat loud inboxes |
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→Calm rooms beat loud inboxes | |||||||
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)
tiktokEvent planning living in 100 email threads? Make ONE shared calendar the boss. Every tool writes to it. No double-booked rooms. (AI-assisted) #eventplanning #operations
instagramTwo days out and nobody knows who confirmed?
Make one calendar the source of truth.
Let AI draft the vendor follow-ups.
#events #eventplanning #operations #productivity #ai
linkedinEvent coordination dies in the inbox. A hundred threads, and two days out nobody can say who actually confirmed. The fix is boring and it works: make one shared calendar the single source of truth, and have every tool write to it. Then let AI read the threads and draft each vendor follow-up, so you wake up to replies already sorted into confirmed, maybe, and chase-again. A calm room beats a loud inbox.
xEvent planning dies in the inbox. One shared calendar = the boss. AI drafts the follow-ups. temerarii.com
facebookIf your event lives in a hundred email threads, nobody knows who confirmed. Here's the fix: one shared calendar is the single source of truth, every tool writes to it, and AI drafts the follow-up to each vendor. You wake up to replies sorted into confirmed, maybe, and chase-again. Want the boring part handled? Visit temerarii.com.
threadsEvent planning dies in the inbox.
Fix: one shared calendar is the boss, every tool writes to it, and AI drafts each vendor follow-up.
Wake up to replies already sorted. A calm room beats a loud inbox.
pinterestEvent coordination tips: make one shared calendar the single source of truth so you never double-book a room, have every tool write to that calendar, and use AI to draft vendor follow-ups and sort replies. Practical event planning and operations workflow for teams drowning in email threads.
blueskyEvent planning dies in the inbox. One shared calendar is the boss; AI drafts the vendor follow-ups. temerarii.com
youtubeRun Events From One Calendar, Not 100 Email Threads
Two days out, nobody knows who confirmed. The fix: one shared calendar as the single source of truth, every tool writing to it, and AI drafting each vendor follow-up so replies arrive pre-sorted. AI-assisted production. Learn the workflow at temerarii.com.