Checklist the per-video bar — engine/sim
86.6/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W38-Fri-1 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 · 62.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–7.3s | spatial-parallax | icon·white-knockout | ♪ bed_in | Old way: a simple payment deal waited on a lawyer, a signature, and weeks of trust on both sides. on-screen: Contracts waited on a lawyer |
expected on screen: red ground · cone hero in the shared Signal Field · Augur leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape coneground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Contracts waited on a lawyer | |||||||
| 2 |  matches intent shared field signature-3d | hook | 7.3–13.6s | kinetic-build | icon·white-knockout | ♪ node_lock | Here is the friction: when neither side trusts the other, every deal needs a slow middleman. on-screen: Trust was the bottleneck |
expected on screen: red ground · cone hero in the shared Signal Field · Augur leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape coneground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Trust was the bottleneck | |||||||
| 3 |  matches intent NumberedList template | teach | 13.6–20.9s | kinetic-build | icon·liquid-chrome | ♪ node_lock | New way: write the rule as code, hold the funds, and release them only when the condition is met. on-screen: Code the rule, escrow the funds |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape coneground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Code the rule, escrow the fundscurate items, nodes | |||||||
| 4 |  matches intent ComparisonTable template | proof | 20.9–27.2s | receipts-count | icon·white-knockout | ♪ node_lock | Now the payment fires the second the work is verified, with no one chasing an invoice. on-screen: Payment fires on the condition |
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape coneground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Payment fires on the conditioncurate colA, colB, rows, statsLabels | |||||||
| 5 |  matches intent BuildLog template | diff | 27.2–34.9s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | Code is literal. It does exactly what you wrote, including the bug, so the edge case is where you live. on-screen: Automation vs the edge case |
expected on screen: red ground · a BuildLog panel over a dimmed Signal Field · Augur leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape coneground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Automation vs the edge casecurate codeLines, lines | |||||||
| 6 |  matches intent ChecklistCard template | teach | 34.9–41.5s | kinetic-build | icon·white-knockout | ♪ node_lock | Teach the rule: write what happens when the deal goes wrong, not just when it goes right. on-screen: Plan every failure path |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Augur leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape coneground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Plan every failure pathcurate items, nodes | |||||||
| 7 |  matches intent KpiGrid template | proof | 41.5–48.5s | receipts-count | icon·liquid-chrome | ♪ node_lock | The refund and the dispute path are the real work, because that is where money actually gets lost. on-screen: The failure path is the work |
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Augur leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape coneground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→The failure path is the workcurate kpis, statsLabels | |||||||
| 8 |  matches intent PipelineMap template | step | 48.5–55.1s | kinetic-build | icon·white-knockout | ♪ node_lock | Your step: take one recurring deal and write every outcome, success and failure, before coding a thing. on-screen: Map one deal's outcomes |
expected on screen: red ground · a PipelineMap panel over a dimmed Signal Field · Augur leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id PipelineMapvisual pipelineshape coneground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Map one deal's outcomescurate stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 55.1–62.1s | coalescence | icon·white-knockout | ♪ bed_out | Now the trust lives in the code, not the wait. The Big T-M designs the failure path first. on-screen: Trust moved into the code |
expected on screen: red ground · cone hero in the shared Signal Field · Augur leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape coneground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Trust moved into the code | |||||||
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)
tiktokA smart contract is just a rule in code that holds funds and releases them when a condition is met. The hard part is the failure path. (AI-assisted) #smartcontracts #web3 #blockchain
instagramCode the rule. Escrow the funds.
Release on the condition.
The failure path is the real work.
#smartcontracts #web3 #blockchain #automation #tech
linkedinA smart contract sounds exotic but the idea is plain: write a rule as code, hold the funds, and release them only when the condition is met. The payment fires the moment work is verified, with no one chasing an invoice.
The catch is that code is literal. It does exactly what you wrote, including the bug. So the real work is the failure path: the refund, the dispute, the deal that goes wrong. That is where money actually gets lost.
Take one recurring deal and write every outcome, success and failure, before coding anything.
xA smart contract is a rule in code that holds funds and releases them on a condition. The hard part is writing the failure path. Method:
facebookA smart contract is just a rule written in code that holds money and releases it when a condition is met. The tricky part is the failure path: refunds and disputes. Comment for a worked example.
threadsA smart contract is not exotic. It is a rule in code that holds funds and releases them when a condition is met, so payment fires the moment work is verified. But code is literal and runs your bugs too. The real work is the failure path: the refund, the dispute, the deal gone wrong.
pinterestSmart contracts explained: how a coded rule holds funds in escrow and releases them when a condition is met, and why designing the failure path for refunds and disputes is the real work. Smart contracts, web3, blockchain, automation.
blueskyA smart contract is a rule in code that holds funds and releases them on a condition. The hard part is the failure path. Method:
youtubeSmart Contracts Demystified: Code the Rule, Design the Failure Path
A smart contract is just a coded rule that holds funds and releases them when a condition is met, firing payment the moment work is verified. This covers why code being literal means the real work is the failure path, the refunds and disputes where money actually gets lost. Smart contracts, web3, blockchain. AI-assisted production.