Checklist the per-video bar — engine/sim
72.8/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-ask-the-operator-W49-Tue good|bad)⚠ 8 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.0s · 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 | hook | 0–5.0s | kinetic-build | icon·wireframe | ♪ node_lock | Outbound question: how many follow-ups before I'm just being annoying? on-screen: "Follow-ups feel spammy" |
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→"Follow-ups feel spammy" | |||||||
| 2 |  first render · fix pending NumberedList templatedead_air | teach | 5.0–10.0s | kinetic-build | icon·wireframe | ♪ node_lock | It's not the count, it's the content. Three follow-ups are fine if each one hands over something useful to read. on-screen: Three, each with value |
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape knotground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Three, each with valuecurate items, nodes | |||||||
| 3 |  matches intent ComparisonTable template | proof | 10.0–15.0s | receipts-count | icon·wireframe | ♪ node_lock | Rewrite your follow-ups so each one hands over something useful, not just a bump. on-screen: Give in every send |
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape knotground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Give in every sendcurate colA, colB, rows, statsLabels | |||||||
| 4 |  first render · fix pending NodeGraphCard templatedead_airgeneric_scene | step | 15.0–20.0s | kinetic-build | icon·wireframe | ♪ node_lock | Ask the Operator |
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Magister leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NodeGraphCardvisual pipelineshape knotground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Ask the Operatorcurate hub, nodes, stages, steps | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 20.0–25.0s | coalescence | icon·ember-fill | ♪ bed_out | Ask the Operator |
expected on screen: black ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Ask the Operator | |||||||
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)
tiktokOutbound question: how many follow-ups before I'm just being annoying?
It's not the count, it's the content.
Rewrite each follow-up so it hands over something useful, not just a bump. Three is fine if each one gives. (AI-assisted)
instagramAsk the operator.
"Follow-ups feel spammy."
It's not the count, it's the content.
Three is fine if each one hands over something useful.
Give in every send, don't just bump.
#outbound #sales #coldemail #buildinpublic #followup
linkedinAsk the operator.
The question: how many follow-ups before I am just being annoying?
It is not the count, it is the content. Three is fine when each one hands over something useful.
Rewrite your follow-ups so every send gives the reader a reason to reply, not just a bump asking if they saw your last note.
Value per send beats volume per week.
x"How many follow-ups before I'm annoying?" It's not the count, it's the content. Three is fine if each one hands over something useful instead of just a bump. temerarii.xyz
facebookAsk the operator: how many follow-ups before you are just being annoying? It is not the count, it is the content. Three is fine if each one hands over something useful. Rewrite your follow-ups so every send gives the reader a reason to reply, not just a bump. More at temerarii.xyz.
threadsAsk the operator.
"How many follow-ups before I'm just being annoying?"
It's not the count, it's the content. Three is fine if each one hands over something useful. Rewrite your follow-ups so every send gives, instead of just bumping the thread.
pinterestOutbound sales tip: how many follow-ups are too many? It is not the count, it is the content. Three follow-ups can work fine if each one hands over something useful. Rewrite your sequence so every send gives the reader a reason to reply, instead of just bumping the thread to ask if they saw your last email.
bluesky"How many follow-ups before I'm annoying?" It's not the count, it's the content. Three is fine if each one hands over something useful instead of just bumping the thread.
youtubeTitle: Ask the Operator: How Many Follow-Ups Before You're Annoying?
The outbound question: how many follow-ups before I am just being annoying? It is not the count, it is the content. Three is fine when each one hands over something useful. Rewrite your follow-ups so every send gives the reader a reason to reply, not just a bump. More at temerarii.xyz.