The visual release. The graph gets a face, without becoming an app. Full detail in CHANGELOG.md.
See it first: sample/dashboard.html is the demo patient's rendered page — download it and double-click. Current status with trends, the event timeline, lab sparklines with reference bands, the active regimen with pharmacogenomic flags, experiments in flight, and symptom frequency, in one file.
How it works
- Run the new DASHBOARD skill (
/dashboardin Claude Code). It reads your graph, serializes the data, and injects it into a fixed rendering shell (templates/dashboard_shell.html). - The shell is versioned and contains all layout and rendering code, so every dashboard from every model on every run looks the same. The skill only supplies data.
- Zero network requests. No CDNs, no fonts fetched, no analytics. The file opens from disk, works offline, and your data never leaves your machine.
- Read-only by hard rule. The dashboard renders; it never edits. Regenerate it when your data changes.
- Responsive at phone widths, empty-state tolerant (new users see a clean page, not nine empty panels), light-only by design in this version.
Also in this release
- PHILOSOPHY.md — why this exists, what I believe, and what this project will never do
- README: "What living with it looks like" — the day-to-day rhythm of an established graph
A note on sharing: the dashboard is one HTML file containing your full health picture — the most shareable artifact this system produces. It saves to reports/, which is gitignored, and the README's sharing guidance applies to it fully.