Checklist the per-video bar — engine/sim
98.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-build-log-W24-Wed good|bad)⚠ 1 flag(s) — not yet ship-ready: copy_generic · 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 · 35.4s · 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.0s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | Week two. We shipped a live GA4 dashboard this week, real traffic numbers, no third-party tool. on-screen: Shipped: GA4 in a dashboard |
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→Shipped: GA4 in a dashboard | |||||||
| 2 |  matches intent BuildLog template | build | 7.0–12.0s | type-on | icon·wireframe | ♪ node_lock | The old move was paying a SaaS to show you charts you already own. on-screen: Old way: paying for a viewer |
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Faber leads · code · type-on · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id BuildLogvisual codeshape boxground blacktreatment wireframemotion type-onpower summoninstrument draw-on→Old way: paying for a viewercurate codeLines, lines | |||||||
| 3 |  matches intent DiffCard template | diff | 12.0–18.6s | crossfade-8f | icon·wireframe | ♪ node_lock | It broke quietly. The API returned empty rows and no error, because the property ID was wrong. on-screen: What broke: empty rows, no error |
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id DiffCardvisual codeshape boxground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→What broke: empty rows, no errorcurate codeLines, lines | |||||||
| 4 |  matches intent WireframeMock template | step | 18.6–23.6s | kinetic-build | icon·wireframe | ♪ node_lock | Now anyone can read their own analytics with a few lines of Python, and the next step is an alert that pings us when daily traffic drops below the seven-day average. on-screen: Next: alert on a traffic drop |
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id WireframeMockvisual pipelineshape boxground blacktreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Next: alert on a traffic dropcurate stages, steps | |||||||
| 5 |  matches intent ComparisonTable template | proof | 23.6–28.8s | receipts-count | icon·wireframe | ♪ node_lock | The proof is public. The dashboard reads our real traffic, wrong turns included. on-screen: Live numbers, public notes |
expected on screen: black ground · a ComparisonTable panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Live numbers, public notescurate colA, colB, rows, statsLabels | |||||||
| 6 |  matches intent shared field signature-3d | resolve | 28.8–35.4s | coalescence | icon·liquid-chrome | ♪ bed_out | Week two of building in public. The bugs ship with the wins. The Big T-M, signing off. on-screen: Bugs ship with wins |
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Bugs ship with wins | |||||||
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 two build log. We shipped a live GA4 dashboard with real traffic numbers and no third-party tool. The old move was paying a SaaS to show you charts you already own. It broke quietly: empty rows, no error, wrong property ID. (AI-assisted)
instagramBuild log, week two.
Shipped: a live GA4 dashboard.
Real traffic numbers. No third-party tool.
Old move: paying a SaaS to show you charts you already own.
What broke: empty rows, no error. The property ID was wrong.
#buildinpublic #ga4 #analytics #python #datadashboard
linkedinBuild log, week two.
We shipped a live GA4 dashboard this week: real traffic numbers, no third-party tool. The old move was paying a SaaS to show you charts you already own.
It broke quietly. The API returned empty rows and no error, because the property ID was wrong. That is the worst kind of bug: it looks like no traffic, not like a mistake.
The payoff: anyone can now read their own analytics with a few lines of Python. Next up is an alert on a sudden traffic drop.
xBuild log wk2: shipped a live GA4 dashboard, real numbers, no third-party tool. It broke quietly: empty rows, no error, wrong property ID. Now anyone can read their own analytics in a few lines of Python. temerarii.com
facebookBuild log, week two. We shipped a live GA4 dashboard with real traffic numbers and no third-party tool, instead of paying a SaaS to show you charts you already own. It broke quietly at first: the API returned empty rows and no error because the property ID was wrong. Now anyone can read their own analytics with a few lines of Python. Want the snippet? Ask in the comments.
threadsBuild log, week two.
Shipped a live GA4 dashboard. Real traffic numbers, no third-party tool.
The old move was paying a SaaS to show you charts you already own. It broke quietly: empty rows, no error, because the property ID was wrong. Now anyone can read their own analytics in a few lines of Python.
pinterestBuild a live GA4 dashboard with Python, no third-party tool. Week-two build log: real traffic numbers pulled straight from the GA4 API instead of paying a SaaS for charts you already own. The common bug: empty rows and no error from a wrong property ID. Read your own analytics in a few lines of code.
blueskyBuild log wk2: shipped a live GA4 dashboard, real numbers, no third-party tool. It broke quietly: empty rows, no error, wrong property ID. Now anyone reads their own analytics in a few lines of Python.
youtubeTitle: Build Log Week 2: A Live GA4 Dashboard in a Few Lines of Python
We shipped a live GA4 dashboard this week with real traffic numbers and no third-party tool. The old move was paying a SaaS to show you charts you already own. It broke quietly: the API returned empty rows and no error because the property ID was wrong. Now anyone can read their own analytics with a few lines of Python. Next up: an alert on a sudden traffic drop.