Skip to content

0006 openweight interchange

github-actions[bot] edited this page Nov 17, 2026 · 1 revision

openweight for import and export, not for storage

Status: accepted · Implementation: planned · Date: 2026-11-17

Evaluated openweight 0.4.0 (openweight.dev).

Context

openweight is an open JSON format for strength training data, licensed Apache-2.0. It defines four schemas (WorkoutLog, WorkoutTemplate, Program, LifterProfile) and ships TypeScript and Kotlin SDKs and a CLI that converts Strong and Hevy CSV exports.

It fits librelifts' aims: local data (ADR 0005) is only really the user's if it can leave in a documented format. But as of 0.4.0:

  • It has no way to express progression: no increments, failure counts or deload rules. That is out of scope by its design.
  • Exercises are identified by name only.
  • It is alpha, with one maintainer, no schema version field yet, and breaking changes expected before 1.0. There is no Swift SDK.

Decision

  • librelifts keeps its own data model, which holds program state and progression.
  • openweight is an interchange format at the edge: export of workout history first, import later. Both are tiered in docs/parity.md; neither is in the MVP.
  • The openweight version is pinned, and the mapping lives in one place.

Consequences

  • Users get an open, documented export next to CSV, and later a way in from other apps through openweight's converters.
  • A breaking openweight release touches one mapping module, not the app's storage.
  • Program state (next weights, failure streaks) does not survive an openweight round trip; a full backup needs librelifts' own format.

Clone this wiki locally