Readiness is context, not the training decision
Readiness scores can be useful. They summarize state, flag fatigue, and help a coach ask better questions. The problem starts when a score is treated as the answer to a different question: what should change in training?
AthDash uses readiness signals as possible context, not as automatic advice. The audit asks whether a driver is tied to a repeatable outcome for this athlete and whether the evidence is strong enough to license a claim.
What the coach still needs
- The likely driver or training lever.
- The outcome it is tied to.
- The effect estimate and interval.
- The caveat that should travel with the decision.
- The no-claim state when the data is too thin.
How AthDash frames the answer
The output is a Driver Card, not a generic readiness alert. It can advise, borrow from a prior, withhold a claim, or decline when the available export history is insufficient.
Readiness
Useful context for the coach, not automatic permission to act.
Driver Card
Names the possible adjustment and the evidence boundary.
Insufficient
When the score cannot support a claim, the audit says so.