Skip to content

fix(ruleset): compare semantic update state - #18

Merged
rldyourmnd merged 1 commit into
mainfrom
fix/ruleset-postcondition-ignore-old-payload
Aug 22, 2026
Merged

fix(ruleset): compare semantic update state#18
rldyourmnd merged 1 commit into
mainfrom
fix/ruleset-postcondition-ignore-old-payload

Conversation

@rldyourmnd

Copy link
Copy Markdown
Contributor

Outcome

Exclude pre-write writable_payload and writable_digest from the immediate semantic postcondition after a ruleset PUT.

GitHub necessarily returns a new writable serialization and digest after a successful update; comparing those to the old CAS evidence made every real update report partial even when all rules, bypass actors, conditions, identity, and enforcement matched.

The full fresh read-back is still recorded and subsequent Verify still compares it exactly.

Evidence

  • regression proves only serialization evidence is ignored
  • semantic rule drift still fails
  • app/provider/ruleset suites
  • quick Go validation
  • portable synthetic fixtures only

@rldyourmnd
rldyourmnd merged commit e312719 into main Aug 22, 2026
2 checks passed
@rldyourmnd
rldyourmnd deleted the fix/ruleset-postcondition-ignore-old-payload branch August 22, 2026 04:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant