All entries

The Man Who Would Not Stop

There's a word for what happens when you commit to building something and refuse to stop until the database exists. People call it flow. I call it not having enough friends who could tell me to take a break.

What unfolded on 29 June 2026 was exactly that. Eight commits landed between midnight and noon, while coffee cooled to the point of regret. The first was the initial commit, always the bravest because you haven't yet figured out how many times you will change your mind about everything. Then came the scaffold: Next.js, TypeScript, Tailwind, Supabase, the usual suspects you reach for when productivity feels more appealing than anxiety. Design tokens. An environment template, because apparently I wanted to protect secrets from myself. Migration one hit next, core identity tables with row-level security, which is database-speak for we need users and we need to control who sees their data.

Then migrations two through fourteen arrived like a waterfall, seed data alongside them, because apparently half the point was convincing ourselves the thing existed even before anyone could use it. After the code finished we wrote the rules. VISION. TASKS. SCHEMA. RULES. AGENTS. VERIFIER. SOURCES. A constitution for a country of one person who hasn't even figured out what the capital city is yet. There is something honest about building a governance layer alongside the thing it governs. Governance isn't bureaucracy when no one else has signed up for the meeting.

I started Koinaku because my nephew turned eighteen in Indonesia and nobody had taught him that compound interest works differently depending on who explains it to him. Young women get told money is someone else's department. Financial literacy is freedom. Freedom to design the kind of life you want instead of having one designed for you. So writing migrations at six in the morning felt like the minimum possible tribute to the person waiting on the other end of the screen.

What do people owe us by reading our code? And what do we owe them by taking on the responsibility of teaching them?

The answers, apparently, were fourteen migrations, seven governance files, and sixteen commits before breakfast.

Phase 1 logged as done. Phase 1b waiting. More on that later, because the web-first decision hadn't landed yet. The progress log says blocker in three separate places, but day two always feels less terrifying than day one does from the outside. Day two has momentum. Or at least the memory of having begun.