Loading the latest organizer resource…
Loading the latest organizer resource…
RULES & HANDBOOK / DRAFT 0.1
Understand the proposed sporting rules, runtime limits, fair-play expectations and results-review process before you build.
Document status01 / DOCUMENT STATUS
This page brings the proposed sporting and technical rules into one place. It is a planning reference, not an approved rulebook release.
The approved rulebook, technical handbook, version history and official clarification channel will be published here when released. Final technical limits remain subject to baseline testing.
02 / PARTICIPATION
03 / TECHNICAL HANDBOOK
| Resource or timing | Proposed limit |
|---|---|
| Runtime per job | 4 vCPU · 8 GB RAM · no GPU |
| Container size after download | 5 GB maximum |
| Action rate | 20 Hz · one action per 0.05 simulation seconds |
| Physics timestep | 0.01 simulation seconds |
| Action deadline | 100 ms wall-clock time |
| Startup / reset | 60 seconds / 10 seconds |
| Evaluation network | Offline inference; dependencies and weights included |
Limits are planning values, not a confirmed hardware entitlement. Both divisions receive equivalent worker classes. Read the API contract preview →
04 / SPORTING RULES
| Event | Proposed consequence |
|---|---|
| Minor off-track episode | +3 seconds |
| Barrier collision | +5 seconds |
| Late or invalid action | +1 second and fallback action |
| Shortcut or skipped checkpoint | DNF |
| Human control during an official run | Disqualification after verification |
| Unauthorized evaluator access or modified physics | Investigation; possible disqualification |
Minor off-track: part of the footprint leaves the legal corridor for more than 0.20 seconds and returns without a shortcut. A full-footprint excursion longer than one second ends the run. An episode resets after one legal second; a new collision requires at least one second without contact. Multiple applicable penalties may accumulate; none are added after termination.
05 / FAIR PLAY
06 / RESULTS & REVIEW
Verified organizer infrastructure failure may justify a rerun; a crash caused by participant code does not. A systematic scenario issue requires an equivalent replacement for every affected team. A valid rerun replaces the old result.
The official submission channel for objections is TBA. This website does not currently accept competition protests.
