Checklist the per-video bar — engine/sim
84.5/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-build-log-W30-Wed good|bad)⚠ 6 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 6 scenes · 36.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–6.4s | spatial-parallax | icon·wireframe | ♪ bed_in | Week eight. We shipped our own CRM this week, built on a database we already had, in a day. on-screen: Shipped: a custom CRM in a day |
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape torusground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→Shipped: a custom CRM in a day | |||||||
| 2 |  matches intent StackTrace template | build | 6.4–15.8s | type-on | icon·wireframe | ♪ node_lock | We almost bought sixty-dollar-a-seat sales software. Instead we modeled contacts, deals, and stages as a few tables and drove them from the terminal. on-screen: Old way: $60/seat sales software |
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Nuntius leads · code · type-on · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id StackTracevisual codeshape torusground blacktreatment wireframemotion type-onpower summoninstrument draw-on→Old way: $60/seat sales softwarecurate codeLines, errMsg, errType, fix, frames | |||||||
| 3 |  matches intent CodeWindow template | diff | 15.8–20.8s | crossfade-8f | icon·wireframe | ♪ node_lock | It broke on duplicates. The same person came in twice from two sources. on-screen: What broke: duplicate contacts |
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Nuntius leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual codeshape torusground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→What broke: duplicate contactscurate codeLines, windowTitle | |||||||
| 4 |  matches intent WireframeMock template | step | 20.8–26.6s | kinetic-build | icon·wireframe | ♪ node_lock | Now the pipeline is ours, not rented. Next, we feed the outbound replies straight in. on-screen: Next: pipe outbound into it |
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Nuntius leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id WireframeMockvisual pipelineshape torusground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Next: pipe outbound into itcurate stages, steps | |||||||
| 5 |  first render · fix pending RankList templatedead_airgeneric_scene | proof | 26.6–31.6s | receipts-count | icon·wireframe | ♪ node_lock | Build Log |
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Nuntius leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape torusground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Build Logcurate rows, statsLabels | |||||||
| 6 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 31.6–36.6s | coalescence | icon·wireframe | ♪ bed_out | Build Log |
expected on screen: black ground · torus hero in the shared Signal Field · Nuntius leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape torusground blacktreatment wireframemotion coalescencepower coalescenceinstrument coalescence→Build Log | |||||||
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)
tiktokWeek eight build log: we shipped our own CRM in a day, on a database we already had. Almost bought $60-a-seat sales software. Instead we modeled contacts, deals, and stages as a few tables, run from the terminal. It broke on duplicates. The fix is next. (AI-assisted)
instagramBuild log, week 8
Shipped: our own CRM, in a day
Skipped: $60/seat sales software
Built: contacts, deals, stages as a few tables
Broke: duplicate contacts
Next: pipe outbound replies in
#buildinpublic #crm #thebigtm #nocode #startup
linkedinBuild log, week eight: we shipped our own CRM in a day.
We almost bought sixty-dollar-a-seat sales software. Instead we modeled contacts, deals, and stages as a few tables on a database we already had, and drove them from the terminal.
What broke: duplicates. The same person came in twice from two sources. We are fixing it with a match-on-email merge. The point is the pipeline is ours now, not rented, and next we feed the outbound replies straight in.
xWeek 8 build log: shipped our own CRM in a day, on a DB we already had. Almost paid $60/seat for sales software. Modeled contacts, deals, stages as a few tables instead. It broke on duplicate contacts. temerarii.com
facebookWeek eight build log: this week we shipped our own CRM in a single day, built on a database we already had. We almost bought sixty-dollar-a-seat sales software, but instead modeled contacts, deals, and stages as a few tables and ran them from the terminal. It broke on duplicate contacts coming in from two sources. Want the schema? Reply and we will share it.
threadsWeek eight. We shipped our own CRM this week, in a day, on a database we already had.
We almost bought $60-a-seat sales software. Instead: contacts, deals, and stages as a few tables, run from the terminal.
What broke? Duplicates. Same person, two sources. Next we pipe outbound replies in.
pinterestBuild-in-public log: how we shipped a custom CRM in one day instead of paying sixty dollars per seat for sales software. We modeled contacts, deals, and pipeline stages as a few database tables and ran them from the terminal. The main bug was duplicate contacts arriving from two sources. Practical no-cost CRM and database build notes.
blueskyWeek 8 build log: shipped our own CRM in a day, on a DB we already had. Almost paid $60/seat for sales software. Modeled contacts, deals, stages as a few tables instead. It broke on duplicate contacts.
youtubeTitle: We Built Our Own CRM in a Day (Build Log, Week 8)
Week eight build log. This week we shipped our own CRM in a single day, built on a database we already had. We almost bought sixty-dollar-a-seat sales software. Instead we modeled contacts, deals, and pipeline stages as a few tables and drove them from the terminal. What broke: duplicate contacts, the same person arriving twice from two sources. The pipeline is ours now, not rented, and next we feed outbound replies straight in. Topics: custom CRM, database design, build in public, sales ops.