docs: is the review loop converging? the measured answer - #332
Merged
Merged
Conversation
…er round Two rounds on 2026-09-12 produced the first evidence good enough to ask whether the review loop drains defects or manufactures them. Recorded rather than remembered, with the method (git blame each finding's file:line at the commit the round reviewed) so anyone can redo it. round two 10 findings, 10 pre-existing (all July), 0 churn by construction round three 13 findings, 8 pre-existing, 5 created by round two's fix (38%) The churn is MORE SEVERE than the drain: the 5 self-inflicted were 3 high and 2 medium with no lows; the 8 pre-existing were 1 high, 2 medium, 5 low. And the drain is real — round three's worst finding predates everything by two months, and 3 of its 8 pre-existing findings were in files round two never opened. Five recommendations, each tied to the evidence that produced it: yield-ordered scope planning, priors for the review seat (mirroring internal/prior, with its disclosure rule), the refuted-claims channel this document described and the code never had, two statically-detectable members of the one-door class, and an origin field on every finding so the ratio is a GROUP BY rather than a person running git blame. The stopping rule: if a round's churn share exceeds the previous round's, stop fixing in batches. The gap is structural — the auditor never builds, so the fix step has no seat, no grading and no record, and that is exactly where the churn lives. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011NgkB3eLPBhgfqU1XopR1V
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two rounds on 2026-09-12 gave the first evidence good enough to ask whether the loop drains defects or manufactures them. The method is
git blameon each finding's ownfile:lineat the commit the round reviewed — churn if the previous fix authored the line, drain if it predates it.The churn is more severe than the drain — the 5 self-inflicted were 3 high / 2 medium / 0 low; the 8 pre-existing were 1 high / 2 medium / 5 low. And the drain is real — round three's worst finding predates everything by two months, and 3 of its 8 pre-existing findings were in files round two never opened.
Five recommendations, each tied to the evidence that produced it, plus a falsifiable stopping rule. Full reasoning in the diff.
🤖 Generated with Claude Code
https://claude.ai/code/session_011NgkB3eLPBhgfqU1XopR1V