Camille Bouvat’s public retrospective says that delivery pressure and too much final delegation to Claude contributed to bugs and to losing familiarity with parts of Saracroche. His correction was function-by-function assistance and AI as a second opinion. The useful Builder Work receipt is that this change in practice maps directly to a repository full of coupled state.
The repo evidence
At commit d9fc924, a remote list is reconciled in ListService, persisted in a shared App Group database, expanded and chunked in BlockerService, then consumed by a different CallKit process. The reset history in PR #175 and its successor shows the team revising how expired and failed patterns become eligible again.
That is why this is not five-minute generated-wrapper work. The hard part is the contract between API input, shared state, a one-action handoff, a separate extension, completion records, retries, and reset rules. Any one function can look reasonable while the boundary is wrong.
The transferable skill
Draw the state loop before asking an agent to change it. Name the source of truth, the serialized handoff, the consumer, the acknowledgement, and the recovery path. Then give an agent one bounded job inside that loop—such as making a reset idempotent or adding a reconciliation test—and review the whole loop, not just its diff. That is how an assisted implementation stays legible to its maintainer.
The public source supports Bouvat’s account of AI-assisted development and the architecture above. It does not prove which lines any tool wrote, that the current App Store binary matches the inspected commit, or that every recovery path is device-tested. A public suite around expansion, removal-before-add, and retry behaviour would be the next stronger engineering receipt.