What is here
Two things. The first is the tools: small programs for infrastructure work and everyday tasks, each built to do one job well. The second is the record of how they are made. The release routes cover getting a Windows app out the door. The field notes collect real build and release failures, the commit that fixed each one, and what the fix does not prove. The AI setup covers running two coding assistants, Claude Code and Codex, side by side so the work never stalls waiting on usage resets. The safeguards are the standing rules for directing a coding assistant without leaking data or shipping the wrong change: the Trifecta Rule, a two-pass review model, and a scan of a repo's full history before it ever goes public.
Why it is in the open
I share this because getting started was hard. Months ago I struggled through it myself, and I would rather the next person have an easier time. The path from a rough idea to a shipped tool has a lot of small traps in it, so the failures are kept right next to the finished tools instead of hidden. The tools are free to try, and the workflow behind them is written down for anyone starting down the same road.