Add sponsor escrow readiness guard#562
Open
Jorel97 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
Summary
Why this slice
This focuses on sponsor-side prize funding readiness before solver submissions open. It is distinct from existing #18 slices for intake/rubric readiness, scoring/arbitration, appeals, communication parity, accessibility/localization, onboarding parity, debrief feedback, withdrawal reimbursement, payout routing, and solver eligibility.
Validation
C:\Users\Juanr\Documents\Codex\2026-05-27\goal-generame-al-menos-200-usd\tools\node\node.exe test.jsC:\Users\Juanr\Documents\Codex\2026-05-27\goal-generame-al-menos-200-usd\tools\node\node.exe demo.jsFFMPEG=... python demo_video.pygit diff --checkDemo video
sponsor-escrow-readiness-guard/reports/demo.mp4sponsor-escrow-readiness-guard/reports/demo.gifSafety
Synthetic data only. No credentials, private challenge data, payment processors, wallets, live escrow providers, production payout systems, or external APIs.
AI-assisted with OpenAI Codex; I reviewed the implementation, tests, generated artifacts, and validation output before submitting.