max / goingson

A context is its own record: the state that frames days Ruled 2026-08-18. Some things occupy your day and others frame it. An occupancy consumes hours and competes for them; a context consumes none, and things happen inside it rather than beside it. Being on leave does not clash with a meeting, it changes what having a meeting means. The code kept making the distinction geometrically. clip_to_day derived is_all_day from whether a span happened to fill a calendar day, so a conference running Wed 14:00 to Fri 17:00 was an occupancy on Wednesday, a context on Thursday, and an occupancy again on Friday. Nothing about it changed but which midnights it covered. This is the record, the migration and the storage. A context is authored as a span and read per day, both ends inclusive, so "off until the 17th" means the 17th is off. Migration 067 converts, as ruled on 8ee5c4fe. A multi-day event becomes a context, where multi-day means it covers a whole calendar day -- narrower than "ends on a later date", so an overnight flight stays an occupancy and a lone all-day marker stays an event. vacation_days becomes spans, and a run crossing two weekly reviews becomes one context rather than two, because nobody recording a nine-day holiday meant two holidays. The conversion guesses, so it is reversible: the event is hidden rather than deleted, the context names it, and deleting the context puts the event back with its times intact. Nothing is reconstructed by hand. vacation_days is not dropped. Dropping it is sync-visible, and the version gate that makes a mixed-version sync safe lives in the SyncKit SDK and does not exist yet, so the column stays as a legacy mirror new code does not write. Contexts are personal rather than group-scoped: sharing "I am on leave" with a project group is a different feature with its own consent question, and adding the column later is one ALTER while taking sharing back is not.