Log your daily step count

End of the day. The watch says 9,500 steps. If the auto-sync didn't pick it up, you tell the agent the number so the day's activity reads honestly — and the weekly step total doesn't end up with a hole where today should be.

What the agent needs to hear

Behind your sentence, the agent works backwards to two pieces: the step count and the date. Count is the only piece you usually have to provide; date defaults to today. « 9,500 » lands cleanly, no unit needed — step counts are always whole counts.

Source is optional but useful when you have it. Naming « from the watch », « from my phone », or « manual estimate » attaches as context so trends downstream know how to weight it. The agent shows a card with the count and waits for a nod. Two seconds, done.

Numbers, dates, and what doesn’t matter

Numbers are flat counts. « 9,500 », « 12k », « about 8 thousand » all parse the same way — the agent rounds fuzzy ones to the nearest hundred. Step counts aren’t precision data; nobody’s PR is « 9,547 », so round numbers are the norm.

Date defaults to today. Named days override: « yesterday », « last Sunday ». If your watch auto-syncs and a value already exists for that date, the agent flags it before overwriting — « there’s already a synced 9,200 for today, replace or keep both? ». Most of the time you confirm replace, because you’re logging precisely because the auto-sync missed.

What this signal is for

Step counts feed three downstream consumers. Daily activity sits next to your training session on the day card, so a strength day with 11k steps reads differently from a strength day with 3k. Weekly step trends show your activity pattern across the week — most people target 7k–10k daily and the trend reads whether you’re hitting that consistently or only on weekends.

Cardio plus step composite combines logged cardio with steps to give a total movement read. A day with no cardio session but 15k steps is a more active day than a day with a 20-minute jog and 4k steps. The step log is the floor — your baseline daily movement. Cardio is the spike on top. Both belong in the picture.

When the agent gets it wrong

Three failure modes show up most. The agent logs steps for the wrong date — you said « yesterday » but it landed on today. Correct it cleanly: « that was yesterday’s count, not today’s ». The log moves to the right day and the running total for today is back where it should be.

The agent treats the count as something else. « 9,500 » in a conversation about weights and rest days can briefly confuse it; push back: « 9,500 steps, not 9,500 kg — that’s a step log, not a weight ». And when an auto-synced value already exists, the agent should surface it before you overwrite; if it didn’t, say so: « there was already 8,200 from the watch — keep that one instead ».

What makes the step log worth keeping

Three things decide whether this step log helps your week read honestly: the count is from a real source (a watch, a phone, or an honest estimate — not a number you wrote down to feel productive), the date is right (a forgotten log added the next day still helps; a wrong-date log corrupts the day it lands on), and the source is tagged when it matters (a manual estimate carries less signal than a watch reading; the trends downstream weight them differently). Step logs round out the activity picture that training sessions alone can’t capture.