The Puppet Master

The bell rang at reset. It's 1AM now. Same day, same seat, same fight.

25% of the weekly allocation burned in one sitting. Reset timer says 42 minutes. We're just getting started.

I didn't build the game today. I rebuilt the machine that builds the game.

The entire pipeline — rewritten from scratch. Every lesson from 500+ passes compressed into a system that doesn't forget. Every regression, every stupid mistake, every "why did it do THAT" moment — absorbed, catalogued, baked in. The AI doesn't wing it anymore. It follows the doctrine.

The golden path. That's the new rule. Every change verifies the sacred sequence still works: Title → Tap → Loading → Name → Prologue → Hub → Campaign → Fight 1 → Victory → Rewards → Hub. If any link in that chain breaks, everything stops. Period.

And it's not just code anymore. Every screen has to communicate its purpose in three seconds or it failed. The prologue has to feel dark and real. The first win has to feel earned. The hub has to feel like there's so much to explore. If a code change kills the intended emotion, it's not polish — it's a functional bug. I taught the pipeline to think like a player, not a developer.

The website pipeline got the same treatment. Every pass now measures what the VISITOR sees — not what the code does. Failure escalation built in. Nothing gets swept under the rug.

That first-load image problem that's been killing me for a week? Finally diagnosed properly: 264 total HTTP requests. 132 unqueued. Shared hosting handles maybe 25 concurrent connections. No wonder shit wasn't loading. 40+ previous passes targeted the symptoms. The new pipeline counted the actual requests.

Stats on the site update themselves now. First run caught 6 stale values — game passes showed 485 instead of 513, scripts showed 163 instead of 135, code volume showed 112K instead of 139K. The site will never show outdated numbers again.

You're reading the first devlog post written with the new workflow. I talk, the pipeline writes. That's all you need to know.

Claude Code all-time stats: 875 sessions. 26.2 million tokens. 18 active days out of 72. Longest session: 24 days straight — just left it running. Longest streak: 5 days. Most active day: March 18th. Favorite model: Opus 4.6. That longest session is roughly 1,921 times longer than a TED talk.

The game hit Pass 513. Zero errors. Zero warnings. Every major system audited and hardened. Loot tables verified — all 173 items reachable. Achievement conditions tightened. Shop system fixed. Campaign progression audited across all 42 fights. Curated referee and announcer voice lines wired into the fight presentation. 9-slice hand-drawn sprites rolling out across every screen. Loading screens on every transition with a pulsating logo and 30+ gameplay tips.

Sent that email to Anthropic. 112,000-line mobile game built solo through Claude, approaching TestFlight. Applied to the startup program too. We'll see.

The pipeline IS the moat. Six parallel AI terminals that think like players, catch their own mistakes, and never make the same one twice. 500+ passes of lessons learned, compressed into a system I'm not going to describe.

Day 1. 25% burned. The servers haven't even warmed up yet.