Checklist the per-video bar — engine/sim
86.6/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W32-Sun-2 good|bad)⚠ 3 flag(s) — not yet ship-ready: copy_genericdup_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 · 50.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·color | ♪ bed_in | For years, posting everywhere meant nine logins and a very long afternoon. on-screen: Posting to nine apps by hand |
expected on screen: white ground · cone hero in the shared Signal Field · Augur leads · node-graph · spatial-parallax · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape coneground whitetreatment colormotion spatial-parallaxpower summoninstrument summon→Posting to nine apps by hand | |||||||
| 2 |  matches intent shared field signature-3d | hook | 5.0–10.2s | kinetic-build | icon·color | ♪ node_lock | Now one push can hit every platform, and you get your afternoon back. on-screen: One push, every platform |
expected on screen: white ground · cone hero in the shared Signal Field · Augur leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape coneground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→One push, every platform | |||||||
| 3 |  matches intent NumberedList template | teach | 10.2–16.5s | kinetic-build | icon·color | ♪ node_lock | An aggregator gives you one account and one key that fans out to all the apps. on-screen: Aggregator: one key, fast start |
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape coneground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Aggregator: one key, fast startcurate items, nodes | |||||||
| 4 |  matches intent RankList template | proof | 16.5–22.8s | receipts-count | icon·color | ♪ node_lock | It is fast to start, but you rent the pipe and a middleman sees your content. on-screen: Trade speed for a middleman |
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape coneground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Trade speed for a middlemancurate rows, statsLabels | |||||||
| 5 |  matches intent LogStream template | diff | 22.8–29.1s | crossfade-8f | icon·color | ♪ node_lock | Going direct to each platform API is harder, but nobody sits between you and the post. on-screen: Your own API: more control |
expected on screen: white ground · a LogStream panel over a dimmed Signal Field · Augur leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id LogStreamvisual codeshape coneground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Your own API: more controlcurate codeLines, rows | |||||||
| 6 |  matches intent ChecklistCard template | teach | 29.1–35.0s | kinetic-build | icon·color | ♪ node_lock | The real move is both: aggregator for the long tail, direct API where control matters. on-screen: Mix both, route by need |
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape coneground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Mix both, route by needcurate items, nodes | |||||||
| 7 |  matches intent StatScoreboard template | proof | 35.0–40.5s | receipts-count | icon·color | ♪ node_lock | We run one queue that decides per post which pipe to send it down. on-screen: One queue, many destinations |
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape coneground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→One queue, many destinationscurate pillar, stats, statsLabels | |||||||
| 8 |  matches intent FlowSchematic template | step | 40.5–45.5s | kinetic-build | icon·color | ♪ node_lock | Start on the aggregator, then graduate the high-stakes channels to direct API. on-screen: Start aggregator, graduate later |
expected on screen: white ground · a FlowSchematic panel over a dimmed Signal Field · Augur leads · pipeline · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id FlowSchematicvisual pipelineshape coneground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Start aggregator, graduate latercurate stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 45.5–50.5s | coalescence | icon·color | ♪ bed_out | That is how you reach everyone without losing your afternoon to it. on-screen: Reach without the busywork |
expected on screen: white ground · cone hero in the shared Signal Field · Augur leads · coalescence · coalescence · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape coneground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→Reach without the busywork | |||||||
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)
tiktokHow we post to 9 platforms at once (AI-assisted). Option A: an aggregator — one key fans out everywhere, fast to start, but a middleman sees everything. Option B: each platform's own API — more work, full control, no one in the middle. The real answer is both: aggregator for the long tail, direct API for the channels that matter. #automation #socialmediatips #buildinpublic
instagramPost everywhere without nine logins.
Aggregator = fast, but you rent the pipe.
Direct API = harder, full control.
The move: use both, route per post.
#socialmedia #automation #contentstrategy #buildinpublic #api
linkedinDistribution choice every content team eventually faces: aggregator or your own API?
Aggregator (Blotato, Buffer, etc.): one key fans out to every platform. Fast to stand up, low maintenance — but you rent the pipe and a third party touches your content and rate limits.
Direct platform APIs: more engineering up front, but no middleman, full control over scheduling, and you own the connection.
The takeaway is not either/or. Run one publishing queue that routes per post: aggregator for the long tail, direct API for the high-stakes channels. You get speed where it is cheap and control where it counts.
xPosting everywhere: aggregator vs your own API.
Aggregator = one key, fast, but you rent the pipe.
Direct API = more work, full control, no middleman.
Do both: route per post. temerarii.com
facebookWant to post to every platform at once? Two paths. An aggregator gives you one key that fans out everywhere — fast, but a middleman handles your content. Going direct to each platform's API is more work but gives you full control. The smart setup uses both, routing each post down the right pipe. Here is how we built ours.
threadsPosting everywhere, two ways: an aggregator (one key, fast, but you rent the pipe) or each platform's own API (more work, full control). Best setup is both — one queue that routes per post. Aggregator for the long tail, direct API where control matters.
pinterestHow to post to all social platforms at once: aggregator tools versus building on each platform's own API. A clear comparison of pros and cons — speed, control, cost, and ownership — plus how to combine both in one publishing queue. Social media automation guide.
blueskyPost everywhere two ways: aggregator (one key, fast, rent the pipe) or direct platform APIs (more work, full control). Best is both — one queue routing per post. temerarii.com
youtubePost to Every Platform at Once: Aggregator vs Your Own API
Publishing to nine platforms used to mean nine logins. Now one push can do it. This short breaks down the two real options: an aggregator that fans out from one key (fast, but you rent the pipe and a middleman sees your content) versus going direct to each platform's API (more engineering, full control, no middleman). The setup we actually run uses both — one publishing queue that routes each post down the right pipe.
Full breakdown at temerarii.com.