How geekdojo builds
Developing with AI
Deep dives on how a one-person shop ships like a bigger one — AI agents doing the quality work, a human accountable for every merge, receipts in public repos.
geekdojo is one person. The output — a cluster OS, a control plane, a firewall image, and the quality system around them — looks like a team, and the difference is a system: AI agents that sweep for duplicated code, review every pull request for security, write fault-detecting tests, watch CVEs, and fuzz the parsers. Agents propose; a human merges. Every mechanism here had to catch something real before it earned trust.
These are the deep dives: how each piece works, how it failed on the way in, and where to find the receipts — everything referenced runs in public repos. The short-form build log lives on the Rasputin devlog; this is the long-form layer.
Deep dives
The first deep-dive is in production. New pieces land here first — subscribe to the feed.