Add sponsor data-room access guard#312
Open
sravan27 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.
Summary
/claim #18
Adds a focused
sponsor-data-room-access-guardmodule for the Scientific Bounty System. This covers the private-challenge handoff between sponsor data release and solver/reviewer workspaces: dataset access grants, NDA and prequalification readiness, least-privilege role checks, expiry and revocation SLAs, stale-token review, audit events, and sponsor remediation packets.This is intentionally separate from existing intake, rubric readiness, scoring, arbitration, appeal, anti-collusion, payout eligibility, IP-redaction, evidence-freeze, clarification-freeze, and award-transparency slices.
Validation
node sponsor-data-room-access-guard/test.js-> 5 tests passednode sponsor-data-room-access-guard/demo.js-> status=hold_data_room, blockers=5, warnings=3node --check sponsor-data-room-access-guard/index.js sponsor-data-room-access-guard/sample-data.js sponsor-data-room-access-guard/test.js sponsor-data-room-access-guard/demo.js-> passedgit diff --check-> passedArtifacts
sponsor-data-room-access-guard/reports/data-room-access-packet.jsonsponsor-data-room-access-guard/reports/data-room-access-report.mdsponsor-data-room-access-guard/reports/summary.svgsponsor-data-room-access-guard/reports/demo.mp4Synthetic data only; no credentials, private sponsor data, or network access.