the fitness log

Pull six months of recovery, sleep, strain, and workouts from WHOOP and lay them out on one page: hero scores, recovery and strain charted together, HRV and sleep trends, all-time personal records, sport mix, and computed patterns.

See the whole picture of training and recovery at a glance, on any device, with no app to open.

A scheduled job refreshes the snapshot from WHOOP once a day on its own, instead of only when Susan opens the dashboard.

The page stays current even on days she doesn't visit, no manual refresh required.

The fixed-template "Today's Call" now reads more than this morning's number: a 3-day recovery trend, a 6-day no-rest-day guard, and sleep debt building up across nights. No LLM yet — no ANTHROPIC_API_KEY is in place, so this shipped as a smarter version of the same deterministic rule set rather than a generated summary. That stays a real option later.

A call that reads the week, not just this morning, with nothing new to keep running.

Gentle loading placeholders while data fetches, tabular numerals so columns of figures line up, and a copy pass over the onboarding page and connection-bar wording.

Smaller rough edges smoothed once the bigger pieces are solid.

A season-level comparison against real, published WHOOP data for a pro athlete. Not one of the numbered phases above — it shipped out of sequence because WHOOP itself published sourced, WHOOP-to-WHOOP season data for the first time, which was the one thing blocking it.

A sense of scale: how your own numbers sit next to a professional's, using only real data from the same kind of device.

A recurring outside critique, not a one-time audit: an independent-designer review run periodically against the live site, checked against this project's own locked design rules (palette, motion, tap targets) and against whether prior recommendations actually got addressed. Not one of the numbered phases — it's a standing practice, not a build with an end state.

Catch design drift as the site grows, instead of only noticing it once it's substantial.

An installable version that adds itself to the Home Screen: its own icon, no browser chrome, and offline reading of the last published snapshot. Same dashboard, no separate codebase, no App Store submission — a web app manifest and a small service worker, nothing more.

One tap from the Home Screen for the check Susan already does every morning, instead of finding a browser tab.

The post-deploy smoke test currently reports healthy or stale, nothing more. Teaching it to tell a dead owner token apart from a WHOOP outage or a rate limit means whoever's debugging starts from the actual cause instead of the same first guess every time. No new service, no new API key, just sharper logic in a script that already runs — the smallest lift of this batch.

A failed check that says what's wrong, not just that something is.

Phase 03 made the same rule-based Today's Call read more of the week. This goes further: with ANTHROPIC_API_KEY finally in place, a daily job could have a model read the week in context and write the call itself, falling back to the tested deterministic version if that call fails. The same direction Phase 03 considered and set aside for lack of a key — the fallback it built is exactly what makes this safe to try now.

A call that reasons about the week, not one that reads it off a fixed table.

A small function that answers a plain question against the last 180 days, instead of only offering fixed charts to interpret. Same data already in the snapshot; a new endpoint and a bit of interface on top, kept owner-only at first to keep the cost of an open-ended question bounded.

Ask "how does this month compare to last spring" and get an answer, not a chart.

Everything today is pull: open the dashboard to learn anything. A scheduled job could watch the same signals Today's Call already flags — a sliding recovery trend, a missing rest day — and only reach out when one actually trips. Needs a delivery channel this project doesn't have yet, most likely email, which is the main reason it sits here rather than earlier.

Hear about it when it matters, instead of finding out on the next visit.

The pro athlete snapshot is hand-maintained: updated whenever WHOOP publishes something new, if someone remembers to check. A standing job could watch for newly published season data and draft the update itself. The least certain item in this batch — WHOOP's press page isn't a formal feed, so this depends on parsing something that could change shape without notice.

One less thing to remember, once it's proven reliable enough to trust unwatched.

The design review cadence's second pass (weighted toward an outside read this time, see maintenance.md) found the visual system itself solid: no locked-rule violations, no pulsing metrics, a page that finally reads as one coherent product rather than several. Its conclusion was that the next move isn't more design, it's restraint — editing down what's already built rather than adding to it.

A product that trusts the person reading it to fill in the gaps, instead of narrating every section and every choice.

Audited alongside the edit-key work on the sibling sites: the dashboard's own "Refresh" button is deliberately open to anyone with the link, no sign-in required, so at first glance it looked like the same kind of gap. It isn't — it's already throttled to once every 5 minutes, timed off the snapshot's own lastUpdated rather than per-visitor, so mashing the button can't burn through WHOOP's rate limit or spam the shared snapshot no matter who's clicking it. That's the right shape of protection for a low-stakes, non-destructive write (worst case was ever an early refresh, never lost data), so no edit key was added here — it would only add friction without closing a real gap.

Already can't be abused by a shared link, without needing a passphrase to use the one button on the page that writes something.