Repository navigation
docs: pinned numbers may move either way with a stated reason - #767
Merged
Merged
Conversation
The ratchet rule said a floor may only rise and a ceiling may only fall, with one exception for a prompt's compiled-size ceiling. The guard can not see a direction: it checks that each pinned value is present in its source file at the recorded number of sites. The rule now says what the guard enforces, plus the record that a move needs. - Any floor or ceiling may move up or down. The entry's description and the PR body give the old value, the new value and the reason. - The lean-prompts goal stays: the bytes that a typical run reads should not grow. A ceiling rise states its reason. - An older description or test comment that states a one-way rule is history. This rule replaces it. Places: CLAUDE.md (Test Ratchets), docs/reference/lean-prompts.md (Rules for every target, rule 1, and Cut rules step 5), docs/reference/file-organization.md, the comment of tests/fixtures/numeric-floors.json and the header of tests/guards/numeric-floor-manifest.test.ts. The guard's non-vacuity probe now moves one site one step down and one step up for every entry, so it shows that a one-file change fails in both directions. The wording pins in tests/docs/lean-prompts-guide.test.ts follow the new text. No pinned value changes. Closes #766
- The manifest comment covers older test comments too, not only descriptions, as the other places say. - The equality-baseline sentence no longer implies that registered entries ratchet in one direction. - The goal lines state the goal as an end state. - The guard failure message names a manifest-only change too. - The file-organization tree note uses full articles and points to the lean-prompts rule, which states the goal. Refs #766
Owner
Author
Evidence: independent audit and resolutionHead: Audit result
Resolution
Tests at the head
|
…site count The tracker-references-guards and test-harness-goldens-budgets knowledge bases now state the either-way rule. The guard header and the manifest comment say exactly, because the presence check and the single-site probe together make the site count exact. No pinned value changes. Refs #766
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.
Summary
The ratchet rule said a floor may only rise and a ceiling may only fall, with one exception for a prompt's compiled-size ceiling. The guard can not see a direction. It checks that each pinned value is present in its source file at the recorded number of sites. This PR makes the written rule match what the guard enforces, and it names the record that a move needs.
descriptionand the PR body give the old value, the new value and the reason.Changes
CLAUDE.md(Test Ratchets): the one-line rule. The file stays at 13,069 chars, under its 13,071 ceiling.docs/reference/lean-prompts.md: rule 1 of "Rules for every target" and step 5 of "Cut rules".docs/reference/file-organization.md: the tree note of the manifest.tests/fixtures/numeric-floors.json: the topcommentonly.tests/guards/numeric-floor-manifest.test.ts: the header, the comments, the failure message and the test titles. The non-vacuity probe now moves one site one step down and one step up for every entry. So it shows that a change in only one file fails in both directions.tests/docs/lean-prompts-guide.test.ts: the wording pins follow the new text.Pinned values
No pinned value changes. A jq comparison of every entry (id, value, pattern, occurrences, description) against
origin/mainshows no difference.Known Limits
numeric-floors.jsonstill say that a value may only rise or only fall. They stay as history, as the issue says. The rule text in each of the five places, except the shortCLAUDE.mdline, says that the new rule replaces them.Tests
tests/docs,tests/guardsand the files that readCLAUDE.md: 96 files, 2,514 passed, 1 skipped.Related Issues
Closes #766