The caller's day on the asking device: the entries and the intervals they cover, in one read

The caller's own day, whatever their role: nobody reads another person's day. Device-bound: without the device header, until the page floor moves, the caller's most recently active device, and no activity with none; 403 for a device not theirs. The day's entries in time order, from every device and source, each with its delivery where the firm has a connector, and the asking device's intervals of the local day in time order, with those of the earlier ids the same machine held that X-Six-Minute-Device-Known names (comma-separated; an id that is not one of the caller's devices is ignored), each on its device's local day, with its evidence, its summary and its activity block and never its judged text: the activity column, where another device's intervals never appear. An entry's evidence is the activity it was generated from: entry_intervals holds, for each live entry of the day generated on another of the caller's devices (the entry's device_id, not the asking device nor an earlier id it names), that device's intervals under the entry (an interval whose start lies in one of its parts), in time order and in the same shape, and nothing else; they are never activity. An entry generated on the asking device, and a hand-made entry (device_id null), read intervals. Never another person's. A slot of an entry with no interval reads "Not captured" (D-217). unit_seconds is the day's unit (the firm's when the day opened, or now for a day not opened yet), the grid of every stretch where no interval is stored (D-219). zone, t_start and t_end are the caller's day row, provisional where the day is not opened yet (the bounds opening it now would store). Each entry carries editable (false once released or while its release is in flight), blockers (what stands between it and a released entry, as rule codes) and options per attribute key. calendar is present only with a calendar connected: the events that overlap the day's bounds, with the caller's marks. Each interval carries judge_order where its matter call read a ranked list: the matter ids, best first. recent_matters is the matters of the caller's own released entries worked in the last 90 days, at most 20, the most recently released first.