Log your bodyweight

Morning, fasted, off the toilet, on the scale. The number reads. You step off, dry your feet, and tell the agent before you start the coffee. One sentence, two seconds.

What the agent needs to hear

Behind your sentence, the agent works backwards to two pieces: the number and when. The unit comes from your profile (kg or lb) unless you override it inline. Date defaults to today; time defaults to the morning-fasted moment most weight logs assume. « 78.3 this morning » carries number, unit (implied), and timing.

If you’re logging a missed day, name it: « yesterday’s weight was 77.8 ». If the weigh-in was at an unusual time (« post-workout, 76.9 »), the agent attaches that as context so the trend reader can flag it later.

Numbers, units, and timing

The number is the only thing you have to say. The unit sticks: « 78.3 » in a kg profile stays kg; « 172.4 » in an lb profile stays lb. To override per entry, name the unit inline: « 172.4 lb » in a kg profile converts and stores both, with the unit you said as the spoken value.

Decimals carry as you give them. Most scales report to 0.1; some to 0.05. Round however your scale rounds — invented precision is worse than honest rounding.

For timing, consistency beats accuracy. A weight logged every morning at 7 am fasted reads differently than one logged some mornings, some evenings, some post-meal. The agent doesn’t enforce this — it logs what you say — but the trend reader leans on consistency to draw a clean curve.

What this signal is for

A weight log feeds three downstream consumers: the weight trend chart (what your weight is doing over weeks and months), the plan adherence layer (if your diet plan has a weight target, the daily reading reads against it), and the readiness signal (rapid weight changes show up in the recovery readiness check).

The trend chart is the highest-value read. One weight is noise; seven daily weights average to a real number; a month of weights tells you whether the plan is working. The system smooths the noise for you — you don’t need to weigh on a fixed day, you just need to weigh consistently in conditions you can repeat.

When the agent gets it wrong

If the number got logged in the wrong unit (« 78.3 » got read as lb when your profile is kg), name it: « that’s 78.3 kg, not pounds ». The card converts and re-saves.

If you logged at the wrong moment in your routine (a post-workout reading you meant to discard, a clothed weigh-in), correct or delete: « delete that one — clothed reading » or « tag it post-workout, not fasted ». And if the date got read off — you said « yesterday » and the agent logged today — push back: « yesterday’s, not today’s ».

What makes the log worth keeping

Three things decide whether this weight log helps you later: the number is what the scale actually read (no inflation, no rounding to feel better), the date and time match the conditions you can repeat (fasted morning is the standard; logging mixed-condition readings noises the trend), and the unit matches your profile or is explicitly overridden (a kg mistakenly stored as lb shifts the entire trend curve). The system reads weight logs as the spine of your body trend; a noisy spine reads as either no progress or false progress, neither of which is true. Weigh in the same conditions, say the number, move on.