01must proveProposed | Opening a record timeline requires activity read permission and read permission for that contact or organization. no proof recorded yet | permission | api | test |
02must proveProposed | Upcoming orders scheduled activities and open tasks from earliest to latest, while History orders completed or cancelled activities and closed tasks from latest to earliest. no proof recorded yet | policy | service | test |
03must proveProposed | An open task uses its due day or, without one, its task date; a closed task uses its task date, positioned at workspace midnight. no proof recorded yet | calculation | service | test |
04must proveProposed | Task rows and task summary counts are omitted when the caller lacks task read permission. no proof recorded yet | permission | service | test |
05must proveProposed | Each shared activity appears once on each linked record’s timeline and contributes once to that record’s summary. no proof recorded yet | invariant | service, database | test |
06Proposed | Timeline filters support type, owner or assignee, outcome, status and time range; selecting an outcome excludes tasks, and selecting the task kind includes them. | policy | api, service | test |
07must proveProposed | Text search matches activity subjects and notes and task titles and descriptions without distinguishing accents or letter case. no proof recorded yet | calculation | service | test |
08must proveProposed | Timeline pages contain 25 items by default and at most 100, continuing across both sources without repeated or skipped items. no proof recorded yet | policy | api, service | test |
09must proveProposed | Past scheduled activities and open tasks due before today carry an overdue flag. no proof recorded yet | calculation | service | test |
10Proposed | An item’s editable flag reflects the caller’s update permission for its record kind. | permission | service | test |
11must proveProposed | The summary aggregates the entire timeline by type and status, lists no more than 200 owners and assignees, and counts upcoming work independently of pagination. no proof recorded yet | calculation | service | test |
12must proveConfirmed | A missing workspace record produces a not-found response; a merged record produces a gone response identifying the survivor. no proof recorded yet | validation | api, service | test |
13must proveProposed | Unknown query parameters and invalid page cursors cause a refusal rather than being ignored. no proof recorded yet | validation | api | test |
14must proveProposed | Both contact and organization activity tabs load their own timelines, and task entries navigate to the task drawer on the Tasks screen. no proof recorded yet | policy | console | observed |