Checklist the per-video bar — engine/sim
100.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review social-W28-Sun-3 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 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 · 51.6s · 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.9s | spatial-parallax | icon·white-knockout | ♪ bed_in | Building software used to mean a team, a backlog, and months before anyone saw it. on-screen: Software meant a team and months |
expected on screen: red ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground redtreatment white-knockoutmotion spatial-parallaxpower summoninstrument summon→Software meant a team and months | |||||||
| 2 |  matches intent shared field signature-3d | hook | 5.9–12.5s | kinetic-build | icon·white-knockout | ♪ node_lock | The spec rotted in a doc while the world moved on, and the demo came too late. on-screen: Specs rotted before the demo |
expected on screen: red ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground redtreatment white-knockoutmotion kinetic-buildpower laser-lockinstrument laser-trace→Specs rotted before the demo | |||||||
| 3 |  matches intent NumberedList template | teach | 12.5–18.8s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Now you describe the feature in plain words and get a running app the same day. on-screen: Describe it, get a running app |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape boxground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Describe it, get a running appcurate items, nodes | |||||||
| 4 |  matches intent ComparisonTable template | proof | 18.8–24.3s | receipts-count | icon·white-knockout | ♪ node_lock | Tools like Claude Code read your repo, write the change, and run the tests. on-screen: Claude Code edits the real repo |
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Claude Code edits the real repocurate colA, colB, rows, statsLabels | |||||||
| 5 |  matches intent DiffCard template | diff | 24.3–29.8s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | What changed: the plain-language spec became the thing that builds, not a dead doc. on-screen: Spec is now the source |
expected on screen: red ground · a DiffCard panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id DiffCardvisual codeshape boxground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Spec is now the sourcecurate codeLines, lines | |||||||
| 6 |  matches intent ChecklistCard template | teach | 29.8–35.7s | kinetic-build | icon·white-knockout | ♪ node_lock | Keep humans on the hard calls, let the agent do the typing and the wiring. on-screen: Keep humans on the hard calls |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Keep humans on the hard callscurate items, nodes | |||||||
| 7 |  matches intent KpiGrid template | proof | 35.7–40.900000000000006s | receipts-count | icon·liquid-chrome | ♪ node_lock | Soon one person describes a tool at breakfast and ships it before lunch. on-screen: One person ships a real tool |
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape boxground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→One person ships a real toolcurate kpis, statsLabels | |||||||
| 8 |  matches intent BlueprintGrid template | step | 40.9–46.4s | kinetic-build | icon·white-knockout | ♪ node_lock | Your step: write a one-paragraph spec for a tiny internal tool, then build it. on-screen: Your step: spec one small tool |
expected on screen: red ground · a BlueprintGrid panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id BlueprintGridvisual pipelineshape boxground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Your step: spec one small toolcurate rows, stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 46.4–51.6s | coalescence | icon·white-knockout | ♪ bed_out | The future is software that ships at the speed you can describe it. on-screen: Ideas ship at the speed of words |
expected on screen: red ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Ideas ship at the speed of words | |||||||
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)
tiktokthe future of building software (and yes, AI-assisted): you describe the feature in plain words, an agent reads your repo, writes the change, runs the tests. the spec stops being a dead doc and starts being the build. #softwaredev #aitools #coding
instagramDescribe the feature.
Get a running app today.
The spec becomes the build.
Humans keep the hard calls.
#softwaredevelopment #aitools #coding #buildinpublic #tech
linkedinTakeaway: the spec is becoming the software. Instead of a doc that rots while a team works through a backlog, you write a plain-language description, an agent like Claude Code reads the repo, writes the change, and runs the tests. Keep humans on the hard architectural calls and let the agent handle the typing and wiring. Software is starting to ship at the speed you can describe it.
xThe future of software: you describe the feature in plain words, an agent edits the repo and runs the tests. The spec stops being a dead doc and becomes the build. temerarii.com
facebookBuilding software used to mean a team, a backlog, and months of waiting. Now you describe a feature in plain words and an agent reads your repo, writes the change, and runs the tests. The spec becomes the build. See how at temerarii.com.
threadsThe future of software: describe the feature in plain words, an agent reads your repo, writes the change, runs the tests. The spec stops being a dead doc and becomes the build. Humans keep the hard calls.
pinterestFuture of software development with AI coding agents: plain-language specs that build running apps, agents that edit your repo and run tests, spec-driven development. AI software tools, vibe coding, agentic development workflow, build faster tips.
blueskyThe future of software: describe the feature in plain words, an agent edits the repo and runs the tests. The spec stops being a dead doc and becomes the build. temerarii.com
youtubeThe Future Of Software: Your Spec Becomes The Build
Building software used to mean a team, a backlog, and months before anyone saw a demo, while the spec rotted in a doc. This short shows where it is going: you describe a feature in plain words, an agent like Claude Code reads your repo, writes the change, and runs the tests. Keep humans on the hard architectural calls and let the agent do the typing and wiring. Software is starting to ship at the speed you can describe it. AI-assisted. More at temerarii.com.