Training logs for cross-country running and skiing teams.
Athletes own their logs. Teams read them here or on their own sites. The format is published, so the data outlives any one tool.
Why this exists
Athletes change teams, coaches, and tools every few seasons. Training history usually stays behind in whatever system last held it. This platform keeps the log with the athlete, in a published format any system can read, so the record survives every transition.
A week in the log (example)
| Day | Session | Time | Zone |
|---|---|---|---|
| Mon | Easy run + strides | 50:00 | L1 |
| Tue | Track intervals: 8 × 1000m, 3:25 each | 1:15:00 | L4 |
| Wed | Recovery run + strength | 1:10:00 | L1 |
| Thu | Threshold: 3 × 10:00 | 1:05:00 | L3 |
| Fri | Rest | 0:00 | none |
| Sat | Roller ski, skate: long | 1:30:00 | L2 |
| Sun | Easy run | 1:00:00 | L1 |
| Total | none | 6:50:00 | none |
In use by the teams Geoff Wright coaches. Not yet accepting other clubs' athletes.
For teams and coaches
- What a team gets
A roster, weekly plans, the schedule, and each athlete's training log and check-ins.
- Data ownership and access
A club's roster, plans, and entries belong to the club. An athlete's log belongs to the athlete. A team reads that log through a grant, which the team can end at any time and which also ends on its own when it expires. The person who runs the site can read what it stores; the security page says exactly who that is and what is recorded.
For developers
- The /v1 contract
A versioned JSON-over-HTTP API. Reads and writes are token-scoped.
The conformance suite
A per-tier test suite. An integration that passes may state the tier it reached, in the wording the brand set gives.
- Security model
Three data classes, scoped tokens, revocable grants. Invites, relinquishments, and token changes are recorded, and so is every authorization denial.