At 11:23am I pushed production to Netlify feeling the kind of quiet confidence that precedes every lesson you will never unlearn about deployments. By 12:04pm koinaku.com had vanished from the internet.
A domain only points in one direction at a time. Vercel was waiting for apex-domain verification. The nameservers lived on Netlify where the lead-gen site needed them for Google Workspace email. You cannot listen to two orchestras simultaneously. Seven commits later we were back on Vercel, accepting that a ten-minute deployment decision had become a four-hour detour through DNS topology nobody asked me to learn.
But here is the thing I remember. While untangling hosting I had already done fifteen other things before lunch.
The OJK sources had broken again because the Indonesian financial authority changed their page layout and returned soft 404s that looked perfect until clicked. We removed those links, remapped what we could verify, and bumped the URL verification timeout. Another commit brought PRD v1.2: MVP release spec, domain model, task breakdown. Written down approximately the fourth time since June, because v1.1 was outdated the moment anyone printed it. Writing is revision. The version number is a flag saying we tried. Foundation Zero, the Money Dictionary mini-track, dropped under its ticket number. A new curriculum section for absolute beginners. Because you cannot explain compound interest to someone who does not yet know what a rupiah is worth.
Assessment gating came through in slices. The app now computes where each user should start based on an initial assessment, publishes micro-lessons through migration 036, and fixes getContinueLesson to return actually available lessons. Analytics arrived alongside it: client and server event trackers, four SQL views for daily active users, activation, retention, lesson completion, first trade. We can now ask questions about retention instead of feeling around in the dark. Email streak reminders wired in next, plus a notification bell sheet so people see red dots instead of wondering why their streak disappeared. Switched from static export to serverless Next.js because static exports do not do crons.
Handoff docs followed. DEPLOYMENT.md, KNOWN_GAPS.md, QA_REPORT.md, ANALYTICS_PLAYBOOK.md. One documentation pass that took longer to write than the features themselves. This too I will stop being surprised by. Probably not today.
Then the hosting flip-flop. Seven commits to recover. Quiet acceptance.
Fifteen commits before noon and no hosting. A new beginner track, analytics views, email reminders, deployment docs written after rather than before the deploy. Some days teach you what you are doing wrong. Others just pile everything else on top while you figure it out.