Why this is public

This isn't a résumé. It's a workshop: small, occasionally strange, mostly-useful systems I build for myself, and the reasoning behind them.

Most of what's here started as a personal itch. Too many repos to track, so I built something to audit them. Agents that forgot what they'd just done, so I built a shared memory for them. An inbox that needed handling without handing it to a cloud, so I built a control plane that drafts but never sends. Dashboards, notification surfaces, repo auditors, a couple of iOS apps, explainers, and a running set of notes from figuring all of it out while the AI boom happens around me in real time.

I made it public for two reasons, and neither of them is "please hire me."

The first is just that the artifacts are more fun to look at than to describe. A live demo, a working tool, a chart that moves: those land in a way a bullet point never will.

The second is the one I care about. Anyone can rent the same model I use; the intelligence is a commodity now. The part that's worth sharing isn't the demo; it's why a thing is shaped the way it is. Why this runs locally and that one is gated behind a human. Why I deleted the clever feature instead of upgrading it. Why the boring mechanism beat the smart one.

The one rule that makes this shareable

There's a reason I can leave this door open at all: everything here is public-safe by construction. You get the architecture and the why: never the data, the contacts, the secrets, or the inside of my actual inbox. That's not a redaction I do nervously at the end. It's the design. The interesting parts of these systems are the decisions, and decisions are safe to show. Anything that isn't safe to show never makes it off the machine, scrubbed deliberately, from a clean copy, before it's ever published.

That rule is liberating, not limiting. It means I can be genuinely open about how these things work without ever being reckless about what they hold.

So: poke around. Read the essays if you want the longer arguments, or the notes if you want the close-ups. Clone the ideas. Argue with me about the trade-offs. This is a workshop: the tools are out on the bench on purpose.