https://backthread.dev/blog/ Notes from Backthread on keeping the reasoning behind AI-authored code — decisions, trade-offs, assumptions — legible to the whole team as agents write more of the codebase. en Mon, 07 Sep 2026 08:20:00 GMT https://backthread.dev/blog/a-merged-pull-request-is-not-evidence-of-understanding https://backthread.dev/blog/a-merged-pull-request-is-not-evidence-of-understanding Mon, 07 Sep 2026 08:20:00 GMT hello@backthread.dev (Jevgeni Bogatyrjov) Every ownership tool you have rests on one assumption, that whoever wrote the code understands it. Agents broke that assumption, and the honest response is to stop scoring people by it. https://backthread.dev/blog/most-agent-written-code-has-no-why https://backthread.dev/blog/most-agent-written-code-has-no-why Mon, 07 Sep 2026 08:10:00 GMT hello@backthread.dev (Jevgeni Bogatyrjov) We extract the reasoning behind agent-written changes and refuse to invent it. Measured on our own repo, 62 percent of decisions carry no alternative and no trade-off. The reasoning was not lost. It never formed. https://backthread.dev/blog/who-on-your-team-understands-each-part-of-the-codebase https://backthread.dev/blog/who-on-your-team-understands-each-part-of-the-codebase Mon, 07 Sep 2026 08:00:00 GMT hello@backthread.dev (Jevgeni Bogatyrjov) Git history tells you who worked where. It stops telling you who understands what the moment agents write the code. A method for building the honest picture, area by area, without quizzing anyone. https://backthread.dev/blog/recording-the-why-behind-ai-authored-pull-requests https://backthread.dev/blog/recording-the-why-behind-ai-authored-pull-requests Tue, 21 Jul 2026 07:00:00 GMT hello@backthread.dev (Jevgeni Bogatyrjov) A Claude Code hook that makes the same agent write down why it opened a PR — Decisions, Trade-offs, Assumptions, Limitations. Local, MIT, nothing uploaded.