Race rules

The format

• Two invited players, one brief, one server-controlled 30-minute clock.
• Bring any AI tool or combination of tools. Shiprace does not connect to them or accept their API keys.
• Submit one self-contained HTML file with inline CSS and JavaScript.

Builds and checks

• Each upload is an immutable version with a SHA-256 file identifier.
• The current version is tested from scratch. Passed checks are never combined across versions.
• Progress means checks passed, not time spent or estimated completion.
• Uploads are limited to 1 MB, 20 versions, and one version every 10 seconds.

The ten public criteria

1. Initial state
2. Add items
3. Edit values
4. Remove items
5. Discount
6. Tax after discount
7. Rounding
8. Invalid input and recovery
9. Reset
10. Mobile usability

Server fixtures use only requirements stated in the brief. A worker infrastructure error is not counted as an app failure.

Finishing

• Locking fixes the current checked version and prevents later uploads.
• At the deadline, the last version fully received by the server is selected. A version received before the deadline may finish checking afterward.
• More passed checks wins. On an equal positive score, the earlier server-received final version wins. Equal score and time is a draw. Two zero scores produce “No qualifying result.”

Comparison and privacy

• Opponent source and preview stay hidden until the race ends. Check progress may be visible.
• Audience comparison uses Build A / Build B and reveals setups only after a vote.
• Audience votes are informal feedback and never change the race winner.
• This casual mode does not prove the absence of preparation, manual code, or undeclared tools.

Tools and costs are self-reported.