Previous value: -"Body weight in kilograms. Convert pounds first (1 lb = 0.4536 kg)."New value: +"Body weight in kilograms (1 lb = 0.4536 kg)."

Previous value: -"Leave empty when recording a measurement the user gives you: the entry is then keyed by its date. An id marks an entry copied from a source document (an export, a spreadsheet); import_document manages those, and recording the same id twice fails."New value: +"Absent for a measurement the user states in conversation: that entry is keyed by its date. An id marks an entry copied from a source document (an export, a spreadsheet); import_document manages those, and recording the same id twice fails."

Previous value: -"What kind of work this is. `cardio` and `mobility` deposit no muscle load at all, so never use them for resistance work — a stretch or a run tagged `compound` lights up the muscle map for days."New value: +"What kind of work this is. `cardio` and `mobility` deposit no muscle load, so they do not describe resistance work; a stretch or a run tagged `compound` shows on the muscle map for days."

Previous value: -"What this exercise is dosed in: 'reps' (the usual case), 'seconds' for holds and carries (plank, dead hang, farmer's walk), or 'minutes' for cardio. It says what the rep range and every logged set's number mean — a 60-second plank is not 60 reps."New value: +"What this exercise is dosed in: 'reps' (the usual case), 'seconds' for holds and carries (plank, dead hang, farmer's walk), or 'minutes' for cardio. It is the unit of the planned target; a logged set keeps reps in `reps` and time in `duration_sec` whatever it is, so a 60-second plank is never 60 reps."

Previous value: -"True when the target muscle is loaded in a stretched position (RDL, incline curl, Nordic curl); false when the stretched half is removed (rack pull, hip thrust, cable kickback). Its residual load persists longer in the muscle load model. Leave null only when you genuinely cannot tell from the movement."New value: +"True when the target muscle is loaded in a stretched position (RDL, incline curl, Nordic curl); false when the stretched half is removed (rack pull, hip thrust, cable kickback). Its residual load persists longer in the muscle load model. Null means unclassified, and the model then infers it from the movement pattern."

Previous value: -"The pattern the movement belongs to (squat, hinge, horizontal_push, …). Keep it the same across variations of one lift: it is how the model judges whether a muscle is already accustomed to that pattern."New value: +"The pattern the movement belongs to (squat, hinge, horizontal_push, …). Variations of one lift share a pattern: the load model judges from it whether a muscle is already accustomed to that pattern, and injury checks match on it."

Previous value: -"The `slug` of the matching entry from search_exercise_pool, when this exercise comes from the curated pool. Set it whenever a pool entry matches — it keeps one movement under one identity even if the display name is later edited or translated."New value: +"The `slug` of the matching entry from search_exercise_pool, for an exercise that matches a curated pool entry. It keeps one movement under one identity even if the display name is later edited or translated."

Previous value: -"The muscles the exercise is done FOR — the prime movers. These alone are counted against the weekly MEV/MAV set landmarks, so list the target, not everything the movement involves."New value: +"The muscles the exercise is done FOR, the prime movers; assisting and stabilising muscles are the secondary and tertiary lists. Only these count against the weekly MEV/MAV set landmarks."

Previous value: -"Muscles that assist meaningfully but are not the target (triceps on a bench press). They count in the muscle load model at a reduced weight. Never repeat a primary muscle here."New value: +"Muscles that assist meaningfully but are not the target (triceps on a bench press). They count in the muscle load model at a reduced weight. The list excludes the primary muscles."

Previous value: -"Stabilisers and minor assistance (abs on a standing press). They count at a further reduced weight. Never repeat a muscle already listed as primary or secondary; leave empty when unsure."New value: +"Stabilisers and minor assistance (abs on a standing press). They count at a further reduced weight. The list excludes primary and secondary muscles; empty means unspecified."

Previous value: -"The calendar date the workout happened, in the USER's timezone. Today only when the conversation is plainly about the session they just did. For anything logged after the fact, take the date from what the user said ('last Tuesday') and ask when that is unclear — never derive one from the server's clock. Everything time-based (weekly volume, the muscle load model, the consistency level) is anchored on it."New value: +"The calendar date the workout happened, in the USER's timezone: the day they did it, which for a session logged after the fact ('last Tuesday') is not today, and which the server's UTC clock does not know. Everything time-based (weekly volume, the muscle load model, the consistency level) is anchored on it."

Previous value: -"Catalog id of the exercise performed. Reuse an id the user already has (`exercise_catalog` in the coaching context, or list_exercises), otherwise a `slug` from search_exercise_pool verbatim. Minting a synonym for a movement that already has an id splits that movement's history in two."New value: +"Catalog id of the exercise performed: an id from the user's catalog (`exercise_catalog` in the coaching context, or list_exercises) or a `slug` from search_exercise_pool, character for character. A new id for a movement that already has one splits that movement's history in two."

Previous value: -"Metres covered, for a carry or an interval the user measured that way ('farmer's walk, 30 metres'). Use it instead of duration_sec when what they said was a distance, not a time; fill both only when they gave both."New value: +"Metres covered, for a carry or an interval the user measured that way ('farmer's walk, 30 metres'). Both distance_m and duration_sec are present only when both were measured."

Previous value: -"Seconds under load for a hold or carry (plank, dead hang, farmer's walk), or the duration of a timed interval. Isometric work is dosed in seconds, not reps. Use it when the user gave a time; when they gave a distance instead, use distance_m."New value: +"Seconds under load for a hold or carry (plank, dead hang, farmer's walk), or the duration of a timed interval. Isometric work is dosed in seconds, not reps. A distance-measured carry or interval is distance_m instead."

Previous value: -"True when the set was done one side at a time. Log it as ONE set whose `reps` holds ONE side's count — never doubled, never split into two sets — and set this flag so the number is read the way it was meant. A timed one-sided hold or carry is per-side too: fill duration_sec, leave reps empty. Logging the same exercise both ways stops it comparing to itself."New value: +"True when the set was done one side at a time. Such a set is ONE record whose `reps` (or duration_sec, for a one-sided hold or carry) is ONE side's count, neither doubled nor split into two sets. An exercise recorded both ways does not compare with itself."

Previous value: -"Reps actually completed. On a per-side set give ONE side's count and set is_per_side — never the doubled total, never two sets. Leave empty for a timed hold or carry and use duration_sec instead."New value: +"Reps actually completed. On a per-side set (is_per_side) this is ONE side's count: not the doubled total, and not split into two sets. Empty for a timed hold or carry, whose dose is duration_sec."

Previous value: -"Reps left in the tank at the end of the set; 0 means taken to failure. Fill it only when the user says how close to failure they got ('had two left', 'went to failure'); a bare 'that was hard' or 'felt easy' is not a number — leave it empty rather than guessing one. It is what tells the model the set's load fades slower."New value: +"Reps left in the tank at the end of the set as the user stated it ('had two left', 'went to failure' = 0); a bare 'that was hard' or 'felt easy' states no number, and then the field is empty. It is what tells the model the set's load fades slower."

Previous value: -"Perceived effort 0-10 — the same question as rir on the other scale (RPE 10 = RIR 0). Use it when the user talks in RPE; rir wins when both are given."New value: +"Perceived effort 0-10 — the same question as rir on the other scale (RPE 10 = RIR 0). It holds a value the user gave in RPE; when both are present, rir takes precedence."

Previous value: -"The client's own stable id for this set, if it has one. Only the AIm app sends this: it lets a later correction be traced to the set that moved, because set_number is renumbered when a set is removed. Other clients have none and leave it out."New value: +"The client's own stable id for this set, if it has one. Only the AIm app sends this: it lets a later correction be traced to the set that moved, because set_number is renumbered when a set is removed. Absent from other clients."

Previous value: -"`working` for real sets. Mark ramp-up sets `warmup`: they are excluded from volume, weekly set counts and the muscle load model, so logging them as working inflates every number the coach reads back. A drop set is not one set: log each weight stage as its own entry in the order performed, the lighter stages `dropset`."New value: +"`working` for real sets, `warmup` for ramp-up sets: warm-ups are excluded from volume, weekly set counts and the muscle load model, and counted as working they inflate every number read back. A drop set is several records, one per weight stage in the order performed, the lighter stages typed `dropset`."

Previous value: -"Load in kilograms: the whole bar for barbell work, ONE dumbbell or kettlebell for dumbbell work. Omit for unloaded bodyweight sets; give only the added weight when the user hangs a plate off a belt."New value: +"Load in kilograms: the whole bar for barbell work, ONE dumbbell or kettlebell for dumbbell work. Absent for unloaded bodyweight sets; for weighted bodyweight work (a plate on a belt) it is the added weight only."

Previous value: -"When the session started, with timezone offset, if the user actually said. Omit it rather than inventing a plausible time."New value: +"When the session started, with timezone offset, as the user stated it; absent when they did not say."

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Previous value: -"The client's own stable id for this set, if it has one. Only the AIm app sends this: it lets a later correction be traced to the set that moved, because set_number is renumbered when a set is removed. Never invent one — omit it."New value: +"The client's own stable id for this set, if it has one. Only the AIm app sends this: it lets a later correction be traced to the set that moved, because set_number is renumbered when a set is removed. Other clients have none and leave it out."

Added value: +"Ignored when recording: every entry belongs to the signed-in user."

Added value: +"Body-fat percentage, 0 to 100."

Added value: +"Body weight in kilograms. Convert pounds first (1 lb = 0.4536 kg)."

Added value: +"Anything worth keeping that has no field above, such as `resting_hr`. Stored and exported, not displayed."

Added value: +"Day the measurement was taken, YYYY-MM-DD in the user's own calendar. Without an id there is one entry per day: recording the same date again adds to that day's entry, overwriting only the fields and keys you send."

Added value: +"Leave empty when recording a measurement the user gives you: the entry is then keyed by its date. An id marks an entry copied from a source document (an export, a spreadsheet); import_document manages those, and recording the same id twice fails."

Added value: +"Circumferences in centimetres, keyed `<site>_cm`. The app shows `chest_cm`, `arm_cm`, `waist_cm` and `thigh_cm`; any other site is stored but not displayed."

Added value: +"Context the user gave with the number (fasted, evening, after travel)."

Added value: +"Where the number came from, free text: `scale`, `tape`, `dexa`, `smart_scale`"

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 128,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The client's own stable id for this set, if it has one. Only the AIm app sends this: it lets a later correction be traced to the set that moved, because set_number is renumbered when a set is removed. Never invent one — omit it."
+}

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Added value: +{
+  "default": "coached",
+  "enum": [
+    "coached",
+    "preserve"
+  ],
+  "type": "string"
+}

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}