Unmarked Racing
Course editor — author points, lines and courses against a chart, snapshot them, and publish what a fleet is handed.
The client — what a boat opens. It asks this device for its position and detects and times your crossings on it, from raw GNSS, with no network. Open it on a phone; it renders on a tablet or a laptop too, at the width it would be in a bracket.
Race screen — running a race: the fleet on a chart in division colours, the start sequence per division, the channel, and whether every boat has seen the latest course. A race is defined in the editor's Races tab; this page conducts one, which is a separate page because there is no undo for telling a fleet to stop.
Test rig — the same client, with a simulated boat and a receiver that lies instead of a real one. Steer it at a line by clicking the chart and watch the Mark screen take over by itself as it closes. Nothing passes from the rig to the phone but a GPS fix, which is the whole point of it.
Still a scaffold. Live Place, the chat and the race-management screens described in wiki/unmarked-racing-brief.html §3 and wiki/client-server-dialog.md are not built, and nothing here posts a record yet. The crossing detector, which is the part that decides a race, is built and specified.
Run the specs in a browser: crossing · race client · mark screen · boat simulator · receiver · client–server dialog · course drawing · geo
Every moment a course became joinable or stopped being joinable. Open to everybody on purpose: what a fleet was handed and when is exactly what a competitor may need to check afterwards, and a record only the club can read is not an audit trail.