Repository navigation
Make the audit's calibration stop harder to skip and easier to act on - #44
Merged
Merged
Conversation
- Run it again after the last batch and gate the summary on it; each verdict table names what comes next - Argue in full only cases naming a drop shape or B.1 failure; cover UPDATEs that delete content - Count claim-neutral fixes as KEEP +fix instead of UPDATE
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
A real 8-batch audit forgot the calibration stop until batch 5, then never re-checked batches 6–8. Its 40-row list was mostly filler arguments; the user acted only on the few real ones, flipping 2 to DROP. Three borderline DROPs were trimmed into UPDATEs that slipped under the old "removed more than it kept" threshold, and format-only fixes inflated the UPDATE count.
The stop now also runs after the last batch, and the summary waits for it. Each verdict table says what comes next. Only cases that name a drop shape or a forcing-function failure are argued in full, and any UPDATE that deletes content is reviewed. Fixes that change no claim count as KEEP.
Test plan
Next: calibration stopafter batch 2, and a second stop after the last batch before the summaryApplies to:placement fix → expect KEEP +fix, counted as KEEP