01must proveConfirmed | Every signed-in console staff member can read and respond to personal attention through baseline use authority, while portal attention remains withheld. | permission | api | observed |
02must proveConfirmed | Audiences resolve during reads through scoped responsibility holders and delegates, direct users and role holders; team audiences currently match nobody. | calculation | database, service | test |
03must proveConfirmed | Ending a holding removes its audience match on the next read without rewriting the occurrence or removing it from other holders. | invariant | service | test |
04must proveConfirmed | Multiple audience matches produce one item with the preferred reason in order: resource responsibility, workspace responsibility, delegation, cover, team, role, escalation and direct user. | calculation | service | test |
05must proveConfirmed | Rank combines class weights of 300, 200 and 100, urgency weights of 60, 40 and 20, allowed adjustments and up to ten daily age points; opportunity cannot outrank required, and displayed due-soon urgency uses workspace calendar days with a seven-day default. | calculation | database, service | test |
06must proveConfirmed | Lists exclude dismissed items and normally snoozed items, support rank, due-date or opening order and cursor pages of 25 by default or at most 100 without duplication or omission. | policy | service | test |
07must proveConfirmed | Summaries group kinds with urgency, snooze and unread counts plus three leading items; unread means required, unacknowledged and unsnoozed, with per-kind counts capped at 500 and reflected on the bell. | calculation | service | test |
08must proveConfirmed | Empty summaries distinguish disabled attention, no holdings or direct audiences, and no outstanding conditions. | calculation | service | test |
09must proveConfirmed | Presentation renders declared facts and scope labels, readable titles and workspace-zone times and durations instead of exposing internal references or raw timestamps. | calculation | service | test |
10must proveConfirmed | An item detail explains its condition, audience match, next action and expected change, concealing occurrences outside the viewer’s audience. | policy | service | test |
11must proveConfirmed | Item actions require their declared permissions and explain missing authority; audience membership itself grants no record or action access. | permission | service | test |
12must proveConfirmed | Record attention shows all open occurrences about that record with personal matches marked, only to an authorized record reader. | permission | api, service | test |
13must proveConfirmed | Reading a colleague’s attention requires read-others authority and creates an audit record. | permission | api | test |
14must proveConfirmed | Attention remains workspace-isolated, and reads without a workspace return no items. | invariant | database | test |