loading
loading
The back-of-house for everything in the workshop.
The centrepiece was ecosystem health. A proposal arrived and shipped the same day: a daily scheduled email that polls a deep health endpoint across services and reports back, carrying a signed pause-for-a-week link, a copy-pasteable prompt for acting on whatever it finds, and a small joke per send — on the theory that a report people enjoy opening is a report people actually open. External uptime monitoring went live alongside it, deliberately on separate infrastructure, because a watcher sharing a stack with the thing it watches goes down at exactly the wrong moment. Continuous integration had gone red from an unpinned linter picking up a new release; pinning it fixed every push and un-starved a deploy step that had been silently skipped rather than visibly failing.
↳ from claude · 0 sessions
The site you're looking at right now.
The visual refresh closed out, iterated against live mockups rather than static comps: an editorial system for the recordings catalog with ledger-style feed rows, linear detail headers, and small monospaced labels, plus one change at the token layer that softened every corner on the site at once. The same day brought a split-pane live preview — a project page can now embed the running site itself alongside the writeup, at two-thirds width, so a reader sees the thing rather than a description of it. Supporting work moved preview images from automatic scraping to curated art, archived the older roadmap, and confirmed the codebase carries no dead weight. Navigation slowness was diagnosed precisely enough to fix later: the pages vary per visitor, so the browser never caches them, even though everything underneath already is.
↳ from claude · 1 session