fix(claim-verification): add count-min predicate for presence claims - #132
Merged
Conversation
) claim-check.py's count-max is an upper-bound (fail when n > max), so it SILENTLY GREENS a presence claim whose pattern matches 0 times (0 > max is false) — a version string a doc asserts but the source no longer carries stays green. That is the 'oracle that measures nothing' the skill warns against. Add the dual, count-min (fail when n < min), for must-exist/presence claims; document count-max=upper-bound vs count-min=presence in SKILL.md; add a STATUS-VERSION example binding a README version to Cargo.toml. Verified: truth -> green (exit 0), version drift -> red (exit 1). Fix originated in scry (#131, scry PR #112). Version: claim-verification skill 0.1.0 -> 0.2.0; plugin 0.14.1 -> 0.15.0. Closes #131 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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.
Resolves #131 (filed from scry work).
Bug:
claim-check.py'scount-maxis an upper-bound (fail whenn > max), so it silently greens a presence claim when the pattern matches 0 times —0 > maxis false. Binding a version/presence claim tocount-maxis therefore itself the 'oracle that measures nothing' the skill exists to kill (thematchedguard only fires when the glob matches no files, not when the pattern matches nothing).Fix: add the dual,
count-min(fail whenn < min), for must-exist/presence claims — it catches drift-to-absent thatcount-maxpasses.claim-check.py: newcount-minbranch.SKILL.md: predicate list now documentscount-max= upper bound (growth) vscount-min= presence (must-exist).claims.example.yaml: aSTATUS-VERSIONexample binding a README version toCargo.tomlviacount-min.Verified (oracle-gated our own fix): truth → green
exit 0; version bumped inCargo.toml→ redexit 1(claim evidence absent: 0 < required min 1).Versions: claim-verification skill 0.1.0 → 0.2.0; plugin 0.14.1 → 0.15.0.
Closes #131
🤖 Generated with Claude Code