Dashboard Guidelines: Days Roll Up to Weeks, Weeks to Day 30, 60, 90

Why Care?

A plan nobody tracks fades by week three. Members also need to show their coach and cohort where they stand without walking them through the plan.

references/dashboard-guidelines.md: data and views, not a technology.
- Two files: tracker.yaml (the plan as numbers: habits with per-week floors and targets, outcomes with Day 30/60/90 milestones) and one log/week-NN.yaml per program week.
- Three levels: days roll up into 7-day program weeks, weeks into the checkpoints.
- Two views: the detailed week for the member, the goals × weeks summary with checkpoint cards for coach and cohort.
- Exact status rules, including the two that matter most: unlogged is never a miss, and a week in progress never reads as a failure.
Agent-agnostic by design. Any assistant, or a person with a text editor, can log. Daily, weekly, or catching up days later all work; entries go under the date they happened.
Templates: templates/tracker.yaml and templates/log-week.yaml.
A reference implementation in references/rendering/dashboard/, copied from mpstaton.com/psp/dashboard: renderer-agnostic rollup logic in tracker.ts, the Astro views, and a fictional sample dataset.
The skill gains Logging and Build a dashboard, and its check-ins no longer assume a daily rhythm or a particular assistant.