Add release note claim evidence guard#539
Open
AlonePenguin wants to merge 1 commit into
Open
Conversation
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.
/claim #10
Summary
repository-release-note-claim-guard/, a focused Project Repository & Version Control slice for release-note truthfulness before tagged repository release or export.Non-overlap
This is not another broad repository ledger, semantic version-tag governor, release signature guard, merge queue, branch-protection drift guard, component-owner approval quorum guard, external reference pin guard, notebook output diff gate, fork provenance auditor, restore rehearsal guard, compute sandbox guard, automation credential rotation guard, artifact prune guard, Git LFS pointer guard, or review-decision provenance guard. It focuses specifically on whether public release notes overstate, omit, or misrepresent the release evidence attached to changed repository artifacts.
Demo Artifacts
repository-release-note-claim-guard/reports/clean-packet.jsonrepository-release-note-claim-guard/reports/risky-packet.jsonrepository-release-note-claim-guard/reports/release-note-claim-report.mdrepository-release-note-claim-guard/reports/summary.svgrepository-release-note-claim-guard/reports/demo-script.txtrepository-release-note-claim-guard/reports/demo.mp4Validation
npm --prefix repository-release-note-claim-guard run checknpm --prefix repository-release-note-claim-guard testnpm --prefix repository-release-note-claim-guard run demonpm --prefix repository-release-note-claim-guard run verify-video-> H.264, 960x540, 4s, 18 fpsgit diff --cached --check -- repository-release-note-claim-guardrepository-release-note-claim-guardreturned no findingsAttempt marker: #10 (comment)
Synthetic data only. No Git provider credentials, private repositories, DOI provider calls, CI systems, payment systems, payout accounts, credential stores, or external APIs are used.
AI-assisted with OpenAI Codex; I reviewed and locally verified the diff before submitting.