Normalise versions to 0.x; correct §8.1 truncation claim#2
Merged
Conversation
- Version notation: spec/protocol is two-component 0.x everywhere (header, §2.1 matrix, §10, CHANGELOG, README badge/status). Only the reference *package* is 0.x.y. conformance.py now parses a two-component spec version (the regex required three components and would have failed on "0.3"). - §8.1: the chain does NOT detect truncation of the most recent receipts (a truncated prefix verifies clean), nor a holder of the local signing key. Added a normative caveat requiring the head be anchored externally for rollback detection, and corrected the false "deleting any receipt breaks a check" line. Matches the honest wording now in the reference's README/SECURITY. validate.py and conformance.py both green; reference 0.2 <= spec 0.3. 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.
Consistency pass on the spec.
0.xeverywhere (header, §2.1 matrix, §10, CHANGELOG, README badge + status). Spec/protocol is two-component0.x; only the reference package is0.x.y.conformance.pyregex fixed — it required three components and would have failed to parse0.3.verify(expected_head=…)hook).No vector or schema changes;
validate.pygreen;conformance.pygreen (reference 0.2 <= spec 0.3).AI assistance disclosure (required)
Kind of change
Checklist
python validate.pygreen ·python conformance.pygreen.