Build logs, release notes, and the thinking behind small self-hostable tools, with the products they are about.

The family grew to eleven this week. The three new names are Korean, not -ing, and that split turned out to mean something. Also, we finally took a family photo.
We ran the experiment again with a different model and asked it to be a hiring manager, not a fan. It was. Part two of a short series where we hand the whole studio to an AI, cold, and publish whatever it says back, kind or not.
We pointed an outside model at the site and the GitHub next to it, with no explanation, and asked it to work out who made this and why. It didn't lead with the tech stack. It found the one sentence every tool is built on.

The fifth tool is a macOS app for planning a program end to end. Its hardest rule is not a feature you can toggle. The database itself refuses to create a file the human never accepted.

The desktop app couldn't reach your Claude login in the keychain. Running the same server from your terminal just works.

Parallel git worktrees, a live board, and merging the winner. A cockpit for agents, with no cloud in the loop.

The model writes layout code; a render scan checks cropping, overlap and typesetting before you ever open the deck.
Why the tools are named the way they are, and the one rule that ties every one of them together.
A short email when something ships or a build log goes up. No spam, unsubscribe any time.