Add challenge reviewer workload SLA guard#412
Open
shaiananvari8 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.
@algora-pbc /claim #18
Summary
challenge-reviewer-workload-sla-guardmodule for the Scientific Bounty System.Scope
This is a challenge reviewer workload and SLA capacity guard. It is distinct from the existing intake, rubric-readiness, scoring/arbitration ledger, reviewer consensus, review-integrity, appeals, anti-collusion, payout eligibility, data-room access, benchmark leakage, cancellation/no-award, license/dependency, human-subjects, withdrawal, embargo-release, evaluator-calibration, and community reputation review-workload slices.
Validation
cd challenge-reviewer-workload-sla-guard && npm run check-> passedcd challenge-reviewer-workload-sla-guard && npm test-> challenge-reviewer-workload-sla-guard tests passed (4)cd challenge-reviewer-workload-sla-guard && npm run demo-> generated JSON/Markdown/SVG artifacts; statushold_review_window, blockers9, warnings3cd challenge-reviewer-workload-sla-guard && npm run demo:video-> generatedreports/demo.avigit diff --check-> passedgit diff --cached --check-> passedrg -n "(password|secret|wallet|paypal|bank|passport|private key|api key)" challenge-reviewer-workload-sla-guard-> no matchesSafety
Synthetic data only. No credentials, private reviewer records, solver identities, payment rails, identity-provider calls, email sends, private challenge workspaces, external APIs, or live challenge mutations are used.
AI-assisted with OpenAI Codex; I reviewed and locally verified the diff before submitting.