Deterministic engine
Fitness, fatigue, form, zones, fueling targets, readiness, and load projections are computed in a pure science layer — unit-tested against literature-minded values, not improvised in a prompt.
Science
We don’t believe in black-box coaching. Koyaro separates the sports-science engine from the conversational layer so every recommendation stays inspectable, adaptable, and honest about uncertainty.
Fitness, fatigue, form, zones, fueling targets, readiness, and load projections are computed in a pure science layer — unit-tested against literature-minded values, not improvised in a prompt.
The language layer helps you plan, fuel, recover, and race — but it is not allowed to invent metrics. When Koyaro answers “why?”, it cites the engine.
Nutrition (including energy-availability awareness), wellness, strength, mobility, and compliance sit beside power data so the prescription reflects the athlete you actually are today.
Overreaching and low energy availability are not growth hacks. The system is designed to surface when less training is the smart call — and to show the signals behind that call.
In the product
Daily calls, ride analysis, and race tactics are not decorative AI. They expose the grounded metrics — readiness, TSB, CTL, compliance, time in zones — so trust is earned in the UI, not claimed in a tagline.

First take
This page is the stance. A deeper public methods note — with references for PMC-style load, carbohydrate periodization, readiness inputs, and energy-availability flags — is on the roadmap as the engine’s documentation surface matures.
Until then: open the product, ask why, and read the numbers the call is grounded in. Or continue with our story and what’s shipping.
Start a trial and interrogate the first daily call — that is the demo.