Checklist the per-video bar — engine/sim
100.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review W35-always-on-beat-2 good|bad)✓ all static checks pass — one-focal/scene · tier-by-beat · one-track caption · colorway · cast+shape correct · no banned/fabricated. (audio + visual tiers verify on the rendered finals — Phase 2)
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 6 scenes · 50.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–8.1s | spatial-parallax | icon·3d-extrude | ♪ bed in | Everybody asks The Big T-M which automation tool to buy, and the honest answer starts with a question nobody likes. on-screen: Picking an automation platform |
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·3d-extrude logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment 3d-extrudemotion spatial-parallaxpower summoninstrument summon→Picking an automation platform | |||||||
| 2 |  matches intent shared field signature-3d | hook | 8.1–15.7s | kinetic-build | icon·color | ♪ — | A stranger picked their tool for their team, their budget, their problems. Not yours. on-screen: Don't copy a stranger's stack |
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Don't copy a stranger's stack | |||||||
| 3 |  matches intent ChecklistCard template | quote | 15.7–23.6s | kinetic-build | icon·color | ♪ — | Our rule of thumb: own the logic so you can leave, and rent only the runtime that runs it. on-screen: "Own the logic, rent the runtime" |
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ChecklistCardshape boxground whitetreatment colormotion kinetic-buildpower summoninstrument shine→"Own the logic, rent the runtime"curate items | |||||||
| 4 |  matches intent RankList template | proof | 23.6–33.900000000000006s | receipts-count | icon·color | ♪ — | We left visual nodes for Claude Code calling tools straight. Plain code moves with you. on-screen: n8n vs Make vs Claude Code |
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape boxground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate rows, statsLabels | |||||||
| 5 |  matches intent shared field signature-3d | hook | 33.9–42.4s | kinetic-build | icon·color | ♪ — | Pick your ugliest weekly task, rebuild just that one in two candidate tools, and let the friction pick the winner. on-screen: Test on one real workflow |
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Test on one real workflow | |||||||
| 6 |  matches intent shared field signature-3d | resolve | 42.4–50.1s | coalescence | icon·3d-extrude | ♪ bed out | We documented the whole migration, no copy-paste, at the hub, so steal the reasoning not the answer. on-screen: temerarii.xyz/build |
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·3d-extrude logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment 3d-extrudemotion coalescencepower coalescenceinstrument coalescence→temerarii.xyz/build | |||||||
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 12 destinations
LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBlueskyEmailSMSBlog
Social captions supplemental published copy · per channel (comp_id level)
tiktokWhich automation tool should you buy? Wrong question. The honest rule: own the logic so you can leave, rent only the runtime that runs it. Test your ugliest weekly task in two tools and let the friction pick the winner. (AI-assisted)
instagramPicking an automation platform?
Don't copy a stranger's stack.
Own the logic. Rent the runtime.
Rebuild your ugliest weekly task in two tools. Let friction decide.
Full migration write-up at temerarii.xyz/build
#automation #nocode #aitools #workflow #buildinpublic
linkedinEveryone asks us which automation platform to buy. The honest answer starts with a question nobody likes: whose problem are you solving, yours or the stranger who recommended it?
Our rule of thumb: own the logic so you can leave, and rent only the runtime that runs it. We moved off visual nodes to Claude Code calling tools directly, because plain code travels and a vendor can't hold it hostage.
The test: pick your ugliest weekly task, rebuild just that one in two candidate tools, and let the friction pick the winner. We documented the whole migration at temerarii.xyz/build. Steal the reasoning, not the answer.
xWhich automation tool to buy is the wrong question. Own the logic so you can leave, rent only the runtime. Rebuild your ugliest weekly task in two tools and let friction pick the winner. temerarii.xyz/build
facebookEverybody asks which automation tool to buy. The honest answer: own the logic so you can leave, and rent only the runtime that runs it. Don't copy a stranger's stack, theirs was built for their problems. Pick your ugliest weekly task, rebuild it in two tools, and let the friction decide. Read the full migration at temerarii.xyz/build.
threadsWhich automation tool should you buy? The honest answer starts with a question people dodge: whose problem are you solving?
Our rule: own the logic so you can leave, rent only the runtime. Test your ugliest weekly task in two tools and let the friction pick the winner. Write-up at temerarii.xyz/build.
pinterestHow to choose an automation platform without copying someone else's stack. The rule of thumb: own the logic so you can leave, and rent only the runtime that runs it. Compare automation tools by rebuilding one real weekly workflow in each. Claude Code, MCP tools, n8n, Make compared. Full migration guide and method at temerarii.xyz/build.
blueskyWhich automation tool to buy is the wrong question. Own the logic so you can leave, rent only the runtime. Rebuild your ugliest weekly task in two tools and let friction pick. temerarii.xyz/build
youtubeTitle: How to Choose an Automation Platform (Own the Logic, Rent the Runtime)
Everyone asks which automation tool to buy, but the platform a stranger swears by was chosen for their problems, not yours. Our rule of thumb: own the logic so you can leave, and rent only the runtime that runs it. We walk through moving off visual nodes to Claude Code calling tools directly, and the one test that settles it: rebuild your ugliest weekly task in two candidate tools and let the friction pick the winner. Full migration write-up at temerarii.xyz/build.