trainlog/docs/exercise_data_model.md

Exercise data model

Status

EXERCISE_DATA_MODEL_V1=PASS
PROFILE_AWARE_DESKTOP=PASS
PROFILE_AWARE_ANDROID=PASS
CONTINUOUS_ACTIVITY=PASS
VARIABLE_REPETITION_SETS=PASS
TRAINLOG_FORMAT_V1=FROZEN

1. Metadata axes

An exercise is described by independent metadata:

recording_mode = SETS | CONTINUOUS
tracking_mode  = REPS | DURATION
data_fields    = supplemental field bit mask

Known supplemental fields:

SPEED_KMH
DISTANCE_KM

Valid model-v1 combinations:

SETS + REPS
SETS + DURATION
CONTINUOUS + DURATION

Invalid:

CONTINUOUS + REPS

UI behavior must never be inferred from an exercise display name.

2. Examples

Presse à cuisses
    SETS + REPS

Gainage
    SETS + DURATION

Marche
    CONTINUOUS + DURATION + SPEED_KMH

Course
    CONTINUOUS + DURATION + SPEED_KMH

Vélo
    CONTINUOUS + DURATION + SPEED_KMH + DISTANCE_KM

Rameur
    CONTINUOUS + DURATION + DISTANCE_KM

3. Load semantics

Load mode is session-specific:

none
external
assistance

external is added resistance.

assistance is help. Lower assistance represents less help and is therefore better when comparing otherwise equivalent performance.

Machine-displayed kilograms are stored faithfully without claiming mechanical equivalence across different machines.

4. Set-based work

SETS + REPS stores one performed-set row per actual set.

Actual repetitions can differ across sets.

Accepted compact repetition input includes:

5x10
4,5,6,7,8,9,10,9,8,7,6,5,4
4..10..4

The pyramid shorthand:

4..10..4

expands to:

4,5,6,7,8,9,10,9,8,7,6,5,4

Each performed row is the source of truth for actual work.

SETS + DURATION likewise stores one actual duration per performed set.

5. Planned versus actual

Desktop-created set sessions may carry explicit planned targets.

Android mobile snapshots can represent actual-only heterogeneous work.

Desktop schema v5 therefore allows an imported set session to have no synthetic uniform target:

target_sets = NULL
target_reps = NULL
target_duration_seconds = NULL

Do not derive a fake target from heterogeneous actual sets.

6. Continuous work

Continuous activity does not ask for:

set count
repetitions
per-set rest
load

Example:

Marche

Durée      45 min
Vitesse    5.8 km/h

Actual persistence uses one continuous_activity record containing duration and configured supplemental values.

No fake performed set is created.

7. Historical interpretation

Desktop session_exercises snapshot:

recording_mode
data_fields

This prevents later catalog changes to those fields from rewriting the meaning of historical rows.

Current desktop tracking mode remains tied to the referenced exercise identity. Any future change to that historical contract requires an explicit schema decision rather than an implicit name-based migration.

8. Android/TUI parity

Both interfaces use the same metadata axes.

The PC -> Android catalog synchronization artifact carries:

exercise_id
name
recording_mode
tracking_mode
data_fields

Creating an exercise inline on Android or desktop follows the same model rules.

9. Exchange boundaries

Frozen Trainlog session JSON v1 remains unchanged.

Synchronization data that exceeds frozen v1 uses separate versioned artifacts.

Continuous activity must never be:

• hidden in notes;
• converted into a fake set;
• silently discarded.

10. Measured max semantics

session_type = max_test is an explicit semantic boundary.

Measured max v1 never equates an ordinary best set with a measured maximum.

For set-based exercises:

external
    max measured load = greatest successful actual load in a max_test

assistance
    best measured assistance = lowest successful assistance in a max_test

none
    measured max = greatest successful reps/duration in a max_test

Ties use greater repetitions/duration.

The newest successful explicit test is the current measured result. A separate same-mode historical record may be older.

No estimated 1RM is mixed into this contract.