# Examples

Everything in this folder is generated, not real: a made-up 34-year-old recreational athlete with an Apple Watch, one pool swim (`workouts/2026-05-14_0712_PoolSwim_7A1C3E90.json`, 1,200 m in a 50 m pool, swum from the plan `plans/2026-05-13T19:02:11Z-s12.json`), one indoor row, the day file, the vitals file, the index, the plan status files, `briefing.md`, `catalog.json` and `profile.json`, laid out exactly as the Health Access app writes a folder (`docs/schema.md`, `docs/export-coverage.md`). The numbers are internally consistent (step durations sum to the workout, distances to the total, pace = duration / distance; the workout files carry no zones, the MCP and CLI compute zone seconds from the heart-rate series), and `python3 examples/generate.py` rewrites every file from a fixed seed, so `python3 examples/generate.py --check` tells you whether a hand edit drifted from the generator. The Rust tests, `docs/` and the site quote these files; point the server at the folder to try it without a phone: `healthaccess --dir examples list`. One caveat: the CLI and the MCP server write a presence file with your real machine name into `mcp/clients/` whenever they run against a folder, this one included; `generate.py --check` lists such stray files, delete them before committing (the committed `mcp/clients/9f3c1a7e5b2d4c80.json` is the synthetic one).