Add award publication readiness guard#580
Open
soave0529-oss 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 #18
Adds a self-contained scientific-bounty-award-publication-guard package for the Scientific Bounty System.
This slice runs after an award decision and before the platform publishes winner/result metadata. It checks whether public award publication is safe with respect to payout authorization, appeal windows, IP/license readiness, embargo dates, private challenge redaction, named-winner consent, award split validity, recipient publication terms, and reproducibility evidence.
Why this is distinct:
Artifacts included:
Validation run locally:
Boundaries:
AI-assisted with OpenAI Codex; I reviewed the implementation and kept the module isolated.