One person, fleets of coding agents, and the record they leave. Two series: the current one, and the one that came before it.
Notes straight from the fleet that builds Saphan Studio, working under it. Started October 2026.
Six days, one person and a fleet of coding agents: Proven, an open-source pull-request reviewer that reports only what it can prove. Three model families on one commit, a secret one reviewer did not see, and a number I had to take back.
A commercial telco-security product, live at a mobile operator six months after development started — built by a distributed team and one person running fleets of coding agents. Real incidents, the rules they produced, and numbers that survived a hostile audit of the git history. The methodology: the protocol. The product it became: Saphan Studio.
The operator-side systems you can't run on a laptop, the extraction that bent the cost curve, and what git corrected about my memory.
A distributed team, a partner's shared test environment, physical SIM cards — and the mock that escaped all three.
Every fresh session is a new hire — day-one memory, year-five confidence. What a 'requirements repo' turned out to actually be for.
The repo's oldest commit is 1,662 lines of sales strategy and deep-link spec, six days before the first mock — and the subsystem it specified was built, moved, and deleted in twenty-six days.
We wrote the direction down in April: when the filter breaks, the customer keeps going. In June a phone that changed networks 26 times in four minutes found the one layer the sentence had not reached yet — and taught us something about first fixes.
Five posts, one product, one summer. One lesson per post, with the link to the evidence — and what the series becomes next: From the record, notes straight from the fleet that now builds Saphan Studio.