Shared contracts¶
Rules and wire formats used by more than one product. Each file says which products implement which side.
| File | What it defines | Used by |
|---|---|---|
| track-sync.md | SLTB binary format, segment rules, upload request and response, tides in the response, golden vector | WatchApp (Garmin, Wear OS), server |
| device-api.md | Device registration, pairing with the 6-digit code, device token, unpairing, platforms, rate limits | WatchApp (Garmin, Wear OS), server |
| vessel-state.md | Vessel states, their wire values (SLTB state byte, FIT developer field) and meaning | WatchApp, DataField, server |
| privacy.md | GDPR rules: no watch request before consent on the watch, stored web consent, full self-service account deletion, information and retention | WatchApp (all platforms), server, every future product |
| calculations.md | Sailing maths shared by watch and server: COG, barometer trend, storm warning, sunrise / sunset, distance and time rules | WatchApp, DataField, server |
The server side of these contracts (endpoints, processing, tables) is in ../server/: api.md, ingestion.md, data-model.md.