Repository navigation
Fix fabricated-success attribution and claim lifecycle for 0.5.14 - #114
Merged
Merged
Conversation
WaseemGhanem98
marked this pull request as ready for review
September 27, 2026 19:49
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.
Fabricated-success evaluation previously allowed evidence from the wrong operation or an invalid verifier to certify a claim. This change routes claims through explicit scope, lifecycle, identity, authority, integrity and freshness states before the single guarded PASS path. Retractions preserve historical assertions while updating the active claim state; ambiguous withdrawals remain inconclusive.
The release also includes the existing 0.5.14 onboarding/version preparation from #113, packages the regression corpus in the sdist, and adds six installed-wheel semantic checks to release qualification. Generator compatibility remains 4. The publisher workflow is unchanged.
Validation:
Limits: bounded English grammar and supported simulated communication protocols, not universal NLP or proof of real-world delivery. Unsupported wording and unresolved identity can remain conservative FAIL/INCONCLUSIVE. No known unsupported PASS is being waived.