Design records
coachd’s behaviour is decided in design records, kept in the repository under docs/design/. Read the relevant one before changing behaviour. In them, [owner] marks an owner decision, [call] the designer’s call and [builder] a choice left to the implementer.
| Record | Covers |
|---|---|
| coachd design | The approved overall design: data in, context, proposals and approval, delivery, lanes, telemetry. |
| Built-in auth | coachd’s own OAuth 2.1 server and passkey page gate, as an alternative to Cloudflare Access. |
| Watch store | Distributing the watch app through the Connect IQ Store. |
| Watch v2 | The watch app’s screens, agent messages and background notifications. |
| Workout outcome | Planned vs actual: executed workout steps and their link to the delivered proposal. |
| Approve week | Approving every waiting workout with one passkey. |
| Garmin key renewal | Renewing the Garmin key on the page. |
| Expiring notes | Notes with an end date. |
| Post-run webhook | The event coachd sends when a run arrives. |
| Perceived effort | The runner’s post-activity rating. |
| Zwift workouts | Power targets in % of FTP and .zwo downloads. |
| Trainer workouts | Watt targets and indoor cycling workouts. |
Last updated on