Repository navigation
The growth census is held by a test, not quoted in a remark - #1187
Merged
Merged
Conversation
`Saturation.RulesUpTo` argues in prose from the split of rules across RewriteRuleGrowth, and the figures it quoted were stale by a factor of four: "26 collect, 17 rearrange, 9 expand and 270 are unjudged", and "84% of the library", all measured before the growth declarations went in. The unjudged count went 261 to 152 over that work; the true split is 97 / 45 / 30 / 152. The argument survives the correction -- a ceiling that refuses Unknown still refuses 47% of the rules, so the dial is still whether unjudged rules may fire at all. The arithmetic in it did not, which is the reason to hold a number somewhere that fails when it moves rather than to reason from it in a comment. RuleAuthoringGuideTest already pinned the 152. It pins all four now, so the next time they move this remark fails with them. Full suite 9564 passed, 0 failed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura
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.
Saturation.RulesUpToargues in prose from how the rules split acrossRewriteRuleGrowth, and the figures it quoted were stale by a factor of four.It said "26 collect, 17 rearrange, 9 expand and 270 are unjudged", and "84% of the library". The real split is 97 / 45 / 30 / 152 — those numbers were measured before the growth declarations went in, which took the unjudged count from 261 to 152.
The argument survives; the arithmetic did not
A ceiling that refuses
Unknownstill refuses 47% of the rules, so the conclusion — that the dial which matters is whether unjudged rules may fire at all, not how far a rule may enlarge — is unchanged. Only the numbers it reasons from were wrong.Which is the point: a number a remark argues from belongs somewhere that fails when it moves.
So it is held now
RuleAuthoringGuideTestalready pinned the 152. It pins all four, so the next time they move this remark fails with them.Found by an audit of #746 tier 2, and verified against the test rather than taken from the audit — the three new counts were unpinned until this PR, so I had no way to check them except by pinning them.
Checks
Full suite 9564 passed, 0 failed, 14 skipped.
🤖 Generated with Claude Code
https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura