Checklist the per-video bar — engine/sim
84.4/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W35-Mon-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 · 55.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 shared field signature-3d | open | 0–5.0s | spatial-parallax | icon·ember-fill | ♪ bed_in | Old social management posted whenever someone remembered, then guessed why it flopped. on-screen: Posting by gut feel |
expected on screen: black ground · octa hero in the shared Signal Field · Lumen leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape octaground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→Posting by gut feel | |||||||
| 2 |  matches intent shared field signature-3d | hook | 5.0–11.3s | kinetic-build | icon·ember-fill | ♪ node_lock | Now we schedule from your own data, not a generic best-time chart from a blog post. on-screen: Schedule from your own data |
expected on screen: black ground · octa hero in the shared Signal Field · Lumen leads · mark · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape octaground blacktreatment ember-fillmotion kinetic-buildpower laser-lockinstrument laser-trace→Schedule from your own data | |||||||
| 3 |  matches intent NumberedList template | teach | 11.3–17.200000000000003s | kinetic-build | icon·wireframe | ♪ node_lock | Pull your last weeks of posts and bucket the engagement by the hour you published. on-screen: Pull your engagement by hour |
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape octaground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Pull your engagement by hourcurate items, nodes | |||||||
| 4 |  matches intent ComparisonTable template | proof | 17.2–23.1s | receipts-count | icon·white-knockout | ♪ node_lock | Your audience has its own clock, and it rarely matches the times the templates promise. on-screen: Your audience has a clock |
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground blacktreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Your audience has a clockcurate colA, colB, rows, statsLabels | |||||||
| 5 |  matches intent JsonDiff template | diff | 23.1–30.400000000000002s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | We run a content calendar, not a panic queue, so each post has a job before it goes out. on-screen: Calendar, not a queue |
expected on screen: black ground · a JsonDiff panel over a dimmed Signal Field · Lumen leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id JsonDiffvisual codeshape octaground blacktreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Calendar, not a queuecurate codeLines, fileName, lines | |||||||
| 6 |  matches intent ChecklistCard template | teach | 30.4–37.0s | kinetic-build | icon·ember-fill | ♪ node_lock | Take one core idea and cut it into native versions, so each platform gets its own shape. on-screen: One core idea, many cuts |
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape octaground blacktreatment ember-fillmotion kinetic-buildpower morphinstrument morph+laser→One core idea, many cutscurate items, nodes | |||||||
| 7 |  matches intent KpiGrid template | proof | 37.0–42.5s | receipts-count | icon·wireframe | ♪ node_lock | Reshaped posts outperform the same file pasted everywhere, every single week we test it. on-screen: Repurposing beats reposting |
expected on screen: black ground · a KpiGrid panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape octaground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Repurposing beats repostingcurate kpis, statsLabels | |||||||
| 8 |  matches intent CheatSheet template | step | 42.5–48.8s | kinetic-build | icon·white-knockout | ♪ node_lock | Step one is reading your own posting hours, then building next week around the live ones. on-screen: Read your hours, then schedule |
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id CheatSheetvisual pipelineshape octaground blacktreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Read your hours, then schedulecurate points, stages, steps, uses | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 48.8–55.099999999999994s | coalescence | icon·ember-fill | ♪ bed_out | A boring, steady rhythm beats a viral fluke. That is how The Big T-M runs social. on-screen: Boring rhythm, real growth |
expected on screen: black ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Boring rhythm, real growth | |||||||
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)
tiktokStop posting by gut feel. Pull your own last few weeks, bucket engagement by the hour you published, and schedule around YOUR audience's clock, not a generic best-time chart. Then cut one idea into native versions per platform. (AI-assisted edit.)
instagramSchedule from your own data.
Bucket engagement by hour.
Your audience has its own clock.
One idea, native cuts per platform.
Reshape, don't repost.
#socialmediamanagement #contentstrategy #socialmedia #marketing #temerarii
linkedinTakeaway for social media managers: ignore the generic best-time-to-post chart.
Pull your own last several weeks of posts and bucket engagement by the hour you published. Your audience has its own clock, and it rarely matches the template. Run a content calendar where every post has a job, take one core idea and cut it into native versions per platform, and you'll beat the same file pasted everywhere. Read your real posting hours, then build next week around the live ones. A steady rhythm outperforms a viral fluke.
xSocial truth: the best-time-to-post chart isn't yours. Bucket your own engagement by hour and schedule around your audience's actual clock. Then cut one idea into native versions per platform. Reshape, don't repost. temerarii.com
facebookOld social management posted whenever someone remembered, then guessed why it flopped. The fix: pull your own last few weeks, bucket engagement by the hour you published, and schedule around your audience's real clock instead of a generic chart. Then cut one idea into native versions per platform. Read your hours, then plan next week. More at temerarii.com.
threadsThe best-time-to-post chart isn't yours. Pull your own last few weeks, bucket engagement by the hour you published, and schedule around your audience's actual clock. Then cut one idea into native versions per platform. Reshape, don't repost. Boring rhythm wins.
pinterestSocial media management guide: analyze your own engagement by posting hour, schedule around your audience's real clock instead of generic best-time charts, run a content calendar, and repurpose one idea into native posts per platform. Evergreen social strategy.
blueskySocial truth: the best-time-to-post chart isn't yours. Bucket your own engagement by hour and schedule around your audience's actual clock. Then cut one idea into native cuts per platform. Reshape, don't repost. temerarii.com
youtubeSocial Media Management: Schedule From Your Own Data, Not Generic Charts
Old social management posted whenever someone remembered, then guessed why it flopped. The method: pull your last several weeks of posts and bucket engagement by the hour you published. Your audience has its own clock, and it rarely matches the template. Run a content calendar where each post has a job, and cut one core idea into native versions per platform. Reshaped posts beat the same file pasted everywhere. A steady rhythm beats a viral fluke.
More at temerarii.com.
#socialmediamanagement #contentstrategy #marketing