Checklist the per-video bar — engine/sim
75.1/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-field-notes-W25-Sat good|bad)⚠ 7 flag(s) — not yet ship-ready: copy_genericlow_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 · 27.1s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  first render · fix pending shared field signature-3ddead_air | hook | 0–5.0s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Field note: we found a flow with twenty-seven nodes wired up to do one small job. on-screen: 27 nodes for one job |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape dodecaground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→27 nodes for one job | |||||||
| 2 |  matches intent NumberedList template | teach | 5.0–11.0s | kinetic-build | icon·white-knockout | ♪ node_lock | The old way wired up trigger, parse, branch, format, send, across a dozen boxes. on-screen: One model call, full job |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Mensor leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape dodecaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→One model call, full jobcurate items, nodes | |||||||
| 3 |  matches intent DiffCard template | diff | 11.0–17.1s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | Find your most fragile flow and ask: could one model with two tools do this. Usually yes. on-screen: Delete a box this week |
expected on screen: red ground · a DiffCard panel over a dimmed Signal Field · Mensor leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id DiffCardvisual codeshape dodecaground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Delete a box this weekcurate codeLines, lines | |||||||
| 4 |  first render · fix pending ProcessFlow templatedead_airgeneric_scene | proof | 17.1–22.1s | receipts-count | icon·white-knockout | ♪ node_lock | Field Notes |
expected on screen: red ground · a ProcessFlow panel over a dimmed Signal Field · Mensor leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ProcessFlowvisual receiptsshape dodecaground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Field Notescurate statsLabels, steps | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 22.1–27.1s | coalescence | icon·white-knockout | ♪ bed_out | Field Notes |
expected on screen: red ground · dodeca hero in the shared Signal Field · Mensor leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape dodecaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Field Notes | |||||||
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)
tiktokField note: a flow with 27 nodes for one job. The old way wired up trigger, parse, branch, format, and send across a dozen boxes. One model call with two tools does the same job. Find your most fragile flow and delete a box this week. (AI-assisted)
instagramField note: 27 nodes for one job.
The old way wired trigger, parse, branch, format, send across a dozen boxes.
Now: one model call, two tools, full job.
Find your most fragile flow. Delete a box this week.
#automation #aiagents #buildinpublic #aimarketing #thebigtm
linkedinField note: we found a flow with twenty-seven nodes doing one job.
The old way wired up trigger, parse, branch, format, and send across a dozen separate boxes. Every box was one more thing that could break.
The new shape: one model call with two tools handles the whole job. Fewer parts, fewer failures.
A move for this week: find your most fragile flow and ask whether one model with two tools could replace it. Usually the answer is yes.
xField note: 27 nodes for one job.
The old way wired trigger, parse, branch, format, send across a dozen boxes. One model call with two tools does the same job.
Find your most fragile flow and delete a box this week.
temerarii.xyz/build
facebookField note: we found a flow with twenty-seven nodes doing one job. The old way wired up trigger, parse, branch, format, and send across a dozen boxes, each one a chance to break. Now one model call with two tools does the whole job. Find your most fragile flow and ask if one model with two tools could replace it. Usually yes.
threadsField note: 27 nodes for one job.
The old way wired trigger, parse, branch, format, send across a dozen boxes. One model call with two tools does the same job.
Find your most fragile flow and ask: could one model with two tools do this? Usually yes.
pinterestField note on simplifying automation: a flow with 27 nodes replaced by one model call with two tools. The old way wired trigger, parse, branch, format, and send across a dozen fragile boxes. How to collapse a brittle automation into a single model call, from The Big T-M.
blueskyField note: 27 nodes for one job. The old way wired trigger, parse, branch, format, send across a dozen boxes. One model call with two tools does the same job. Find your most fragile flow and delete a box this week.
youtubeTitle: 27 Nodes, One Job | Field Notes | The Big T-M
A field note from the bench: we found an automation with twenty-seven nodes doing one job. The old way wired up trigger, parse, branch, format, and send across a dozen separate boxes, each a chance to break. One model call with two tools does the same job. The move: find your most fragile flow and ask whether one model with two tools could replace it. Usually yes. Method-only, no hype.