August 2026
Why a marketing site gets prerendered
Evidence should not be contingent on a bundle finishing.
A single-page React app renders nothing until its JavaScript runs. That's fine for a screen behind a login. It's a problem for a page that reviewers, resume parsers, and link-preview crawlers reach first — because a lot of them don't run your JavaScript, and the ones that do still judge you on the first paint.
So this site prerenders. The words are in the served HTML before a line of script executes. The claim that we ship product is not something you have to wait for a bundle to reveal — it is right there in the markup, the way a claim about shipping ought to be.
July 2026
The Perpetual Beta, honestly
A narrow promise, not an excuse.
'Perpetual beta' is easy to say and easy to abuse. It can quietly mean 'never finished' or 'never accountable.' We mean something narrower: ship the smallest thing that actually works, put it in front of real people, and let contact with reality set the next move.
Version 1.0 is a starting line. The discipline is in what you do after it ships — the bug you reproduce, the metric you actually read, the thing you cut — not in the promise you make before.
June 2026
One person, governed like an org
The agents make the standard cheap to hold. They do not set it.
Running an engineering organization with one human and a fleet of agents sounds like a shortcut. In practice it is the opposite: it only works if the rules are written down, the gates are real, and the hard stops are honored even when they are inconvenient.
The agents do not make the standard. They make it cheap to hold — to review every change from three angles, to keep the decision log current, to refuse a merge that skipped a gate. The standard still has to come from somewhere, and be enforced by something.