Every task creation bumps two counters per junction: the due time in minutes-since-midnight, and the reminder offset in minutes before due. The composer asks for the top three of each and shows them as chips labelled 'your usual'. Sourceless entries act as a fallback pool so habits carry between junctions once established.
Also called: learned reminder times · your usual time · smart defaults · no invented times
- 1POST /api/tasks fire-and-forget upserts into task_time_prefs on (user, source, kind, value), incrementing uses.
- 2GET /api/tasks?prefs=<source> returns the most-used three due times and three reminder offsets for that junction.
- 3Fixed offsets already on screen are filtered out of the learned list so nothing is offered twice.
Migration 175 states the rule verbatim: “rule: the composer must never recommend arbitrary times. No '9am because 9am seems nice' — a suggestion is only legitimate once it reflects what this person really picks at this junction. Someone who always sets pipeline follow-ups for 7:00 AM should be offered 7:00 AM, and someone who has never used the composer should be offered nothing.” The composer repeats it: 'There are deliberately NO fixed time-of-day presets anywhere in this composer.'
- Invented default times that fit nobody
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →