No CSS framework
Design tokens in :root, one CSS Module for layout, flat single-class selectors. Tailwind and a component library were both on the table and both left off — at this size they are more config than code, and I would rather own the cascade than debug someone else's.
No client components
Every component here renders on the server, so the HTML arrives complete and nothing of mine hydrates. Next's App Router runtime still ships with it, and the scroll reveal is a dozen-line inline script that watches for content entering the viewport — the one piece of my own code that runs in the browser. A page with no client components is not a page with no JavaScript, and I would rather say that than round it down to zero. The rest of the motion lives in the stylesheet: the health panel boots its rows on first paint, content below the fold slides in once as it comes into view, and one pulsing dot repeats through the nav, the panel, the release rows, and the contact pill.
No numbers I can't defend
An earlier draft of this page carried p99 latencies and pipeline pass rates. I had not measured any of them, so they came out and nothing replaced them. What is here now is tooling and dates, and every line of it traces back to work I actually did.
on call · johnrey-altamarino