A record you can trace back to.
MovePacket is being built as a dependable system of record for athlete data. The first foundation is an original file that stays unchanged, a stable activity ID, and inspectable processing details.
A system of record preserves evidence and its history. It does not certify that every sensor measurement is accurate or that an application’s interpretation is correct.
What the beta records#
| Evidence | Available today |
|---|---|
| Original | Exact uploaded FIT bytes, authenticated download |
| Integrity | SHA-256 checksum and original byte size |
| Receipt | Activity creation time after storage accepts the original |
| Processing | Current status and an error code when processing fails |
| Derived data | Decoded JSON, wrapper schema version, decoder package/version and FIT profile when ready |
| Access boundary | Workspace-scoped API and browser access |
| Portability | Original FIT, decoded JSON and record metadata export |
Identical bytes uploaded within one workspace reuse the activity ID. This does not identify two different files as the same real-world session. Cross-source duplicate reconciliation is planned.
Inspect and verify a record#
Open an activity in your workspace and choose Record. This view is available even if decoding has failed or is still processing.
Verify original reads the preserved FIT and compares its SHA-256 checksum and byte size with the activity metadata. A match confirms that the retrieved bytes match the stored record. It does not verify device calibration, athlete identity, consent or coaching conclusions.
Export record details downloads a JSON snapshot containing the activity ID, intake route, receipt time, original checksum/size, current processing state, available parser metadata and retrieval links. It contains no API keys. It is current metadata, not an access audit or full transformation history.
Download the original and decoded JSON separately when moving the activity into another system. The quickstart also demonstrates checksum verification from your server.
Where the record stops today#
The beta does not record a provider account connection, verified athlete identity, athlete consent, delegated app grants, access history or a complete sequence of reprocessing versions. Missing links are shown as unavailable rather than inferred from device fields.
Per-athlete and app permissions, revocation, richer source provenance, transformation history, restore tooling and self-service deletion remain planned. There is no claim that the current beta is a complete compliance solution or a complete business records system.
Shared responsibility#
MovePacket operates the storage, file processing and workspace access in this service. It preserves source files and provides authenticated retrieval and integrity verification.
Your coaching business establishes permission to use athlete data and determines how it should be used. Your application must enforce its own end-user permissions, protect downloaded copies and server keys, and control its coaching recommendations and decisions. The current workspace key is not an athlete-specific grant.
The intended product direction is to make these responsibilities easier to meet with built-in access controls, traceability and portable records. Operational responsibilities need to be supported by the service terms and applicable data-processing arrangements; this guide does not assign legal controller or processor status.
Evidence before interpretation#
Keep original evidence separate from derived results. When your software computes aggregates or prepares context for AI, retain the activity references, source window, units, missing-data information and method version needed to explain the result.
Coaching judgments, readiness scores, training recommendations and race strategy belong in the application built on MovePacket. See the data model for the beta’s exact fields and units.