01must proveConfirmed | Responsibility registration validates an application’s complete list and rejects foreign keys, unsupported scope or derivation objects, unknown roles and missing fallback areas without partial writes. | validation | service | test |
02must proveConfirmed | Registration updates changed areas, skips unchanged ones, retains omitted areas as retired and replaces role defaults. | lifecycle | service | test |
03must proveConfirmed | Changed registrations reconcile operational workspaces within a 30-second budget, initializing defaults and uncovered-area state, with remaining work deferred to nightly processing. | lifecycle | service | test |
04must proveConfirmed | Nightly reconciliation creates declared role defaults, respects removed defaults, ends undeclared ones and makes no changes on an identical rerun. | lifecycle | service | test |
05must proveConfirmed | An always-held area without a workspace-level active primary appears in the unassigned report, updated atomically by assignment changes and cleared when coverage returns. | calculation | service | test |
06must proveConfirmed | Unassigned areas produce advisory attention for administrators and clear when covered, with post-write attention refresh failures leaving the responsibility write successful. | policy | service | test |
07Confirmed | Responsibility readers can inspect uncovered areas and follow their assignment links. | permission | api, console | test |
08must proveConfirmed | Applications synchronize record-derived holdings through a function that inserts missing holdings and ends obsolete ones without deleting history. no proof recorded yet | invariant | database | observed |
09must proveConfirmed | Derived synchronization requires the transaction’s workspace and actor, a valid application and derivation key, an array of active responsibility entries declared derivable from that application’s objects with people, allowed holder kinds, valid scopes and ordered dates, and no repeated responsibility at a scope; it serializes each derivation, validates before writing, refreshes changed dates and audits inserts, endings and refreshes in the same transaction. no proof recorded yet | validation | database | observed |