Race Practice

Availability notice

Race Practice is planned. The Solo shape is specified. The Duo and Trio shapes are specified. The platform implementation ships in a future release. This page describes the planned behaviour so the format is documented even before the implementation lands.

This page tracks the planned design. It updates as Race Practice ships.

What Race Practice is

Race Practice is a self-reported training context that lets an athlete rehearse an official CCB race flow without a coach or Judge controlling the Session. The same engine runs. The reporting authority is different.

The governing principle:

Same Session Engine. Different reporting authority.

Everything below follows from that.

How Race Practice reuses the Session Engine

Race Practice does not introduce a second Session Engine. It uses the same engine the platform already runs for Group Sessions and (eventually) Competition.

Concretely, Race Practice:

• uses the canonical 12-station layout;
• runs the same 60-second Work Phase;
• uses the same Freeze boundary at the minute mark;
• runs the same Evaluation against the per-station target;
• generates Burdens with the same Assignment logic;
• shares the same session-state broadcast and recovery behaviour;
• stores results in the same athlete-history storage.

What Race Practice changes is who drives the lifecycle and what the results mean. It does not change how a single Work Phase behaves.

Who owns the Session

In a Group Session, the coach owns the Session lifecycle. In Race Practice, the athlete who started the practice owns it. This owner is the Race Practice Owner.

The Race Practice Owner:

• starts the practice;
• drives the lifecycle in place of a coach (advances past Decision Points, ends the practice);
• cannot edit another athlete's result;
• cannot override Evaluation;
• cannot cancel a rule-generated Burden;
• cannot declare a team total.

The platform still owns the timing and the Evaluation. The race-practice owner owns the operational decisions a coach would normally make.

Who owns the result

Every athlete owns their own result. The platform computes the team total from each athlete's confirmed input — never the other way around.

• Individual result. The athlete types their result at the Freeze.
• Team total. The platform sums the confirmed inputs. The platform never asks an athlete to enter a team total directly.
• Aggregation. Different station categories use different aggregation rules (sum for distance, sum for reps). The rule is documented and version-pinned; the platform cannot change it mid-Session.

This is what makes Race Practice usable as preparation. The athlete rehearses the entire protocol, including the moment of confirmation, with no observer deciding the outcome for them.

Evaluation and Burdens in Race Practice

Evaluation in Race Practice is deterministic — there is no coach discretion. The platform runs the same Evaluation it runs in a Group Session and produces the same outcome from the same input. Burdens are generated the same way.

This is the rehearsal promise: what the athlete experiences in Race Practice matches what competition produces. If Evaluation depended on a coach's judgement, the rehearsal would not match the thing it is preparing the athlete for.

What Race Practice is not

A few things look similar but are deliberately separate:

• Not a Coach session. There is no coach role. The Race Practice Owner is an athlete.
• Not official. Results are private training records. They never enter official rankings, are never Judge-verified, and never qualify the athlete for anything.
• Not a second engine. The platform reuses the Session Engine. Race Practice is a context, not a parallel implementation.
• Not collaborative completion. A Race Practice is completed by the athletes who started it. The room of an athlete's Race Practice is the athletes they chose to include; the platform does not invite outside participants.

Formats within Race Practice

Race Practice will support the four official formats in turn.

Race Practice Solo is specified and ships first. Couple and Trio Race Practice reuse the same engine with team aggregation over individual inputs and ship afterwards.

Reporting authority and result ownership

The reporting authority is what differs from a Group Session or Competition.

• Group Session. Coached. Results may be official practice records at the facility.
• Competition. Judge-verified. Results enter official rankings and qualification.
• Race Practice. Self-reported. Results are private training records only.

The Result page covers the difference in full. The short version: the lifecycle and the engine are the same; the reporting authority is what makes Race Practice a rehearsal rather than an official outcome.

Incomplete practice

A practice that ends mid-Session is marked incomplete. Incomplete practice is preserved — never silently rewritten as a finished practice — and is visible only to the athlete who started it. A future record-keeping decision may surface this status to the athlete's history view; the principle is that incomplete work stays incomplete, never inflated to a complete result.

Why Race Practice exists

Race Practice exists because preparation is the difference between the athlete who arrives at a race ready and the athlete who does not. The format's standardization only matters if the athlete can rehearse it. Race Practice is how an athlete rehearses the full protocol under race-like conditions, with no observer present, on the same engine Competition will use.

The page will update as Race Practice ships.