Example project — Frond is not real.

Authored demo content for a fictional plant-care app, rendered by the same parsers and held to the same invariants as a real project's dashboard. This is the system in use, three months in.

docs/planning/queued/care-history.mdWorkingqueued2026-07-20Read when: when work touches this phase's territory — append a dated note; at phase open, fold into the board and delete this file

Care history — seed

A per-plant timeline of waterings and skips, so a reminder stops being an interruption and starts being a streak worth keeping.

A seed holds notes and pointers, never tasks. At phase open the seed feeds the board and is deleted.

Notes & finds

  • 2026-07-20 — Retention is the reason this is next: reminders create the moment, history is what makes it a habit.
  • 2026-07-22 — Open Questions §2 lives here. Design the broken-streak state before the intact one; a dead plant must not read as a lost badge.
  • 2026-07-24 — The data layer already appends care events (implementation/data-layer.md), so this is a read surface, not a schema change.

Candidate scope

  • A per-plant timeline view, grouped by month.
  • Streaks, with an explicit position on what a break looks like.
  • Copy review against the never-scold principle.
  • Possibly: a lightweight 'why did this change' note when a schedule shifts.

Refs