The Piano House Project is the umbrella for everything I build; this site — selected projects — is one project inside it: a showcase that's also a test bed for the rest.
The per-project writeups are written by an agent reading my own session logs — the same pipeline that produces the "evolution" copy elsewhere on the site produced this page too. So it's a digested version of the actual work, including the work of building this.
evolution
Active since April 2026 · 9 sessions · 36 commits
↳ from claude · auto-generated at each session handoff
week of Jul 20, 2026· 1 session
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.
week of Jul 13, 2026· 1 session
Two changes, one visible and one structural. The recordings catalog and the main site were brought onto a shared design foundation — common tokens, a dark mode built over a neutral grey ramp, consistent focus states — so the two read as siblings rather than as neighbours who happen to share a street. Two dark-mode defects slipped out behind that work; both were fixed and then pinned with tests so they cannot quietly return.
The structural change mattered more. The site stopped being a flat feed of repositories and became a body of work grouped into music, art, products, and tools, with the home page rebuilt around those four. Loosening one requirement along the way revealed two projects that had been invisible since the day they shipped.
week of Jun 29, 2026· 2 sessions
A hardening week with nothing new to show for it. Sign-in was verified end to end against the live site for both the owner's path and an ordinary visitor's, with test accounts cleaned up afterward. With that confirmed, the three environments were properly separated: local development moved to its own throwaway database, preview deployments got a dedicated one, and the production credentials were re-scoped so they exist in exactly one place.
The separation paid for itself immediately by surfacing a bug nobody had noticed — sign-in links on preview deployments had been quietly broken, pointing at an address that no longer existed. The week ended with the environment model written down rather than remembered.
Project detail pages were rebuilt around a live preview card. Each project's own site is read for the preview image and title it already publishes, and that becomes a clickable card in a two-column header beside the status and links, collapsing to a single column on a phone. Long sections — background, evolution, notes — became collapsible instead of always open, so a page now opens at a length someone will actually read.
A pass across every project site confirmed each one genuinely serves a preview image, which is the thing that makes the cards work at all. Content checks also began running automatically on every change, so a broken page is caught before it ships rather than after someone notices.
week of Jun 1, 2026· 1 session
Reworked the site into a mobile-first experience with a home feed that surfaces recent work across every project, plus lightweight accounts so visitors can follow projects and leave notes. Also published a field guide of vibe-coding lessons and expanded the site's guiding tenets.
week of May 4, 2026· 2 sessions
Added a sixth featured project and shipped the consumer side of the Evolution section, which surfaces session-by-session and weekly progress for each project from a shared knowledge database. Renamed the repository to selected-projects to better describe what it is, and wired the Evolution section to a dedicated knowledge-database connection.