The Always-On Server.
An old laptop, plugged in and left on — the private machine everything else now runs from.
It started as a disk problem. My Mac kept running out of room — every code build, every cache, every regenerable heavy thing piling up on the one machine I actually work on. So I took an old laptop, plugged it in, and turned it into a server that never sleeps. Servers are always-on by definition; this one earns the name.
The regenerable weight lives there now, and on a drive beside it — build artifacts, caches, the things you can always rebuild — off the Mac, which stays lean and fast. That was the whole point, and then it became the substrate for everything else.
It hosts my private records myself, so nothing that is only mine sits on rented infrastructure. A key on the box means I can query my own data and run the Soma coach on demand — from wherever I am, whenever I want.
It is wired to years of journals through a bridge, but a careful one. The systems are connected; the data is not cross-read. Nothing crosses the boundary it should not, even though the whole thing is my own build on my own hardware. Privacy-conscious by construction, not by trust — the same hard, one-way discipline the rest of the private work holds to.
The real work was never the box. It was reading and reconciling the state across three machines — laptop, phone, server — and routing cleanly between them so they behave as one thing. Once that held, the payoff arrived: I can develop from anywhere. Claude Code from my phone, the Mac from a table somewhere else, every project landing on the machine that’s always on. Reachable from anywhere over a private mesh; exposed to no one.