What does not work yet, told before it works.

The problem: The simulator produces coordinates and captures in every session. Until now, comparing a rider’s session with the one they did a year ago meant opening two reports side by side.

The work: Python development to read, normalise and compare those outputs inside the athlete history, with the interpretation logic that is applied by hand today written out as explicit rules.

Where it stops: It is an internal support layer. It decides no adjustments, replaces no session, and has not yet been used to produce a single recommendation given to a rider.

The problem: Motion capture takes setup time and stable lighting, which limits how many repetitions fit into a session.

The work: Tests with Orbbec depth cameras to speed up capture and increase the number of observed repetitions per session, checking their output against the current system.

Where it stops: It is in comparison testing. Until that comparison closes, session capture continues on the system already validated.

The problem: Postural and joint-range assessment consumes a large share of the session, and part of that measurement depends on the hand taking it.

The work: Evaluating the purchase of a VALD HumanTrak system to standardise postural and movement tests, document them and compare them between sessions under the same protocol.

Where it stops: It is not in the laboratory yet. Strength, ranges and asymmetries are measured today with the VALD DynaMo Plus dynamometer, which is operational.

The problem: With enough cases, regularities appear that the eye does not catch: combinations of restriction, asymmetry and geometry that tend to end in the same complaint.

The work: Models trained on in-house data to classify and flag patterns worth a second look, together with language models for summarising long histories.

Where it stops: No model output reaches a report without someone reviewing it. A correlation found in in-house data is not a clinical claim and is not published as one.

The problem: A six-month process produces repeated measurements the rider currently sees as separate reports, with no curve showing whether anything moved.

The work: Building an in-house view showing what changed, by how much and since when, in language that does not require reading a spreadsheet.

Where it stops: Not operational. It will be announced here and on the technology page when it works, not before.

The problem: Course simulation already projects power, pace and time, but treats rider drag as a reference value rather than something measured case by case.

The work: Work on drag coefficient, rolling resistance and frontal area so that a race projection starts from your actual position instead of an average.

Where it stops: A line of exploration. Projections delivered today state the assumptions they were built on.