Rhythm

The Rhythm page surfaces patterns your household has built up over the last 8 weeks of task and routine completions. HoneyDone uses these to help you plan around the tendencies that already exist, rather than prescribing new ones.

What you'll see

Four kinds of pattern cards:

• Weekly rhythm — e.g. "You usually do house & yard on Sunday". Grouped by the context mode (desk work, errands, house & yard, phone & admin) your completions most often carry.
• Time of day — e.g. "Your desk work happens in the morning". Buckets: morning (5a–11a), midday (11a–4p), evening (4p–9p), night (9p–5a).
• Co-occurrence — e.g. "You often do Dishes and Laundry on the same day". Detected when two distinct task titles are completed on the same calendar day across 3+ separate days.
• Anomaly — shown in amber. e.g. "phone admin has slowed down — down 60% this month". Fires when the last 4 weeks has dropped 30%+ compared to the previous 4.

Each card shows a confidence bar, an observation count, and the date it was last computed.

Guardrail: we never show patterns with fewer than 3 observations

This is a hard rule. One-off events don't become patterns. If you just started using HoneyDone you'll see an empty state instead — come back after a few weeks of activity.

How it's computed

A nightly cron job (02:00 server time) reads your last 8 weeks of completed tasks and routine executions, computes the day of week and time-of-day bucket in your household's timezone (not UTC), and aggregates them into patterns. High-confidence (60%+) clusters also feed HoneyDone's existing recommendation engine — there is no separate rhythm-only recommendation layer.

Notifications

The first time a pattern crosses the 3-observation threshold, HoneyDone sends a one-time notification ("New rhythm noticed") to each active household member. Subsequent recomputes of the same pattern do not re-notify.

Privacy

Rhythm computation runs entirely inside HoneyDone. No data is sent to third parties. Observations are keyed by task / routine execution IDs and carry only the domain tag (context mode) and title in metadata.