One Pass

Pass 642. Zero errors. Zero warnings.

I know because a file told me.

I'm obsessed with logs. Every pass writes itself down before it moves on. What changed, what broke, what held. Redundancy by design. Developing without logs is catching falling knives — you might grab the handle, mostly you just get cut.

People think the moat is speed. Parallel terminals, parallel passes, tokens evaporating. It's not. The moat is that nothing I've ever done on this project is lost. Pass 23 from February. Pass 513. Pass 641 from earlier today. Every single one. Every decision, every regression, every "why the fuck did I do it like that" moment — written down the second it happened, while the context was still warm.

33 devlog entries public. Hundreds of pass files private. Devlog is the highlight reel. The pass files are the tape.

I can't lie to myself. If a pass introduced a regression it's in the file. I can't pretend Pass 488 went clean when Pass 489 exists specifically because 488 broke something. Regressions can't hide when everything is written down.

The proof showed up today.

---

Website Pass 168.

Started as a single-number fix. The site said 139K lines of code. The repo said 120K. A 14% inflation on the one thing I care about more than anything. My whole pitch is transparency and the site was lying. Not on purpose. Drift. The number had been right once, months ago, and nobody updated it when the code actually moved.

Nuclear audit. Every number, every page, every auto-reply email.

Scripts said 135+. Actual 139. Voiced scenes said 57. Actual 55. Items said 375+. Actual 385+. Audio said "3,600+ files" — conflating voice lines, music, and sound effects into one inflated soup. Killed it. Replaced with 243 music tracks, the only number I could verify. Companions said 11. Actual 13. Achievements said 85. Actual 110 total, 85 visible, 25 hidden — reframed honestly because burying the hidden ones was its own kind of lie.

The honesty cuts both ways. Some numbers were understated. Fixed those too.

Then the Apollo 11 line. Somewhere in the planning I'd drafted a comparison — "nearly twice Apollo 11's codebase." Killed it before it shipped. Not worth the fact-check landmine. Once you write "nearly twice" publicly you can't walk it back. Every number on the site now has to survive a hostile reader with a calculator.

Build duration was the subtle one. "8 weeks" was hardcoded. I'm at 12 weeks. Would have kept drifting every week forever. Ripped it out. Built a system that reads the current week from an anchor date and calculates live.

MVP status flags said "Audio Sync READY" and "Mobile Build TestFlight ready." Neither is true. Changed both. Better to disappoint on the homepage than at TestFlight.

Devlog count, pass counts, script count — all now read from one file. Single source of truth. Site, PHP email templates, everything pulls from the same place. Week counter auto-increments. Devlog count bumps when I add a post (this one bumps it to 34). Pass counters bump when the pipeline logs a pass.

I can't drift anymore. The architecture won't let me.

And because this pass touched everything, the pipeline wrote itself a new rule on the way out: no file ships to staging without a stat cross-check against the repo. Every value, every inline number, every email template. Before any deploy. No exceptions. Every pass that modifies a deployable file now creates a timestamped backup folder with a full rollback document. This pass created the first one. Template for every pass after.

---

Audit. Architecture. Discipline upgrade.

One pass.

One.

47 minutes.

Zero rollbacks. Zero regressions. Still Pass 168 end to end.

---

Screen recorder running on my desktop, capturing the best track off each of the 9 Spotify albums one at a time — clips for Instagram stories going out over the next few days. Site updating live in the tab next to it. FileZilla green. Every dynamic stat resolving clean. Backup folder on disk, receipts intact. Email templates pulling from the right source.

Epic came up in the rotation.

A track I wrote as a Suno prompt four months ago not knowing what I was doing. Cleaned up, named, uploaded to DistroKid, waited a week for Spotify to ingest. Playing on Spotify right now while I screen-recorded it to post on Instagram to market a game I built from nothing to validate a pipeline I designed that just executed a pass I'd planned for an hour and a half in 47 minutes first try.

A perfectly machined zero-tolerance part.

A tear rolled down my cheek.

I sat there for a second.

---

Then the waitlist pinged.

Fighter 16.

27 days of me filling my own form. Every fighter before today had been me testing my own signup flow. The waitlist was my own test emails sitting there pretending to be users.

Fighter 16 wasn't me.

Someone I don't know read the site, liked it enough to put their email in the box, and clicked submit. While I was still processing that, Fighter 17 came in. Two strangers. Back to back.

The counter actually started today.

Someone liked it enough to wait for it.

Then I logged the pass.

---

Pass 642. 120K lines. 13 scenes. Website Pass 168. Epic album on loop. One tear. And a folder of files that remembers everything I didn't.

Logs don't lie.

Get back up.