01must proveConfirmed | Application attention declarations are validated together, rejecting foreign keys, changed classes, unexplained required classes, escalating opportunities, incompatible audiences, invalid templates, unavailable actions or permissions and foreign about-objects. | validation | service | test |
02must proveConfirmed | Removing a declared kind retires it and resolves its open workspace items while retaining workspace settings. | lifecycle | service | test |
03must proveConfirmed | Applications publish and resolve attention within their transaction through four restricted database functions, rejecting foreign workspace or service claims and unavailable kinds, while Platform can evaluate any application’s computed kinds. | permission | database | test |
04must proveConfirmed | Item publication rejects invalid facts, scope chains over ten or an organization scope placed before the end, unsupported or excessive audiences, missing responsibility targets, teams, unknown product roles and non-Platform eligibility audiences, rolling back refused writes. | validation | database | test |
05must proveConfirmed | Each kind and deduplication key has one open occurrence, refreshed in place with replacement audiences while retaining escalations; recurrence after resolution creates a new generation. | invariant | database | test |
06must proveConfirmed | Published surfaces reflect the kind’s and workspace’s choices, and scope chains end at the workspace after application-provided resource ancestry. | calculation | database | test |
07must proveConfirmed | Resolution reports whether it closed an open occurrence and safely repeats; unconfirmed resolution clears matching occurrences not refreshed since a given instant, optionally within a scope. | lifecycle | database | test |
08must proveConfirmed | Closed occurrences do not reopen; a 15-minute sweep expires overdue expiry dates, releases their deduplication keys, clears recently retired kinds, refreshes rank and removes orphaned supporting records. | lifecycle | service | test |
09must proveConfirmed | Scheduled computed attention uses reporting data to publish matching records and clear missing matches, stopping above 100,000 without clearing items and rejecting eligibility audiences until customer authoring exists. | policy | service | test |
10must proveConfirmed | Manual resolution requires its separate permission and an audited reason, returning not found for an occurrence already closed. | permission | api | test |
11must proveConfirmed | Monthly attention storage retains 13 months, dropping remaining open occurrences with their partition for providers to recreate on a subsequent sweep. no proof recorded yet | lifecycle | database | test |
12must proveConfirmed | Contact and organization merges redirect attention references and audiences to the survivor, including a merged contact’s personal state. | lifecycle | database | documented |
13Confirmed | Attention does not automatically create tasks or messages and currently emits no business lifecycle events. | policy | service | documented |