Check judge access, preserve the submitted commit and reproduce a documented demo. Copy the acceptance record and track each blocked step.
·2 min read
Steps
Agree the access and repair rules
Check the submitted version
Record a repeatable scenario
A reusable record for checking whether a submitted project is accessible and whether its documented scenario can be reproduced. Technical acceptance does not determine a competition score or confirm production readiness.
For each submission, copy the record below into your event's approved working space. Use a submission identifier instead of participant names. Keep private links, credentials, recordings and raw logs in the approved restricted location.
Agree on the rules before submissions open
Specify the required artifacts and accepted submission channel.
Publish the deadline and time zone.
Require a fixed version identifier for the work being reviewed.
Define who can approve access repairs or changes after the deadline.
Explain whether a backup recording is accepted and what it can demonstrate.
Assign an acceptance coordinator and a route for disputes.
Do not put secrets or personal data in this record. A passing scenario confirms only the stated scenario in the recorded environment. A video does not confirm behavior on a new input. Preserve the original evidence when a repair is approved.
