--- id: WF-PFM-ELG-013 title: Hand responsibility cover to a colleague trigger: >- A holder or manager arranges temporary cover for personal holdings, or an authorized party ends that cover. product_area: platform module: eligibility revision: 1 status: draft design_intent: confirmed origin: >- Responsibilities and attention architecture D-07 (delegation in phase 1), approved by Andrew 2026-10-18 (PLAT-M15 "Decisions"); PLAT-M23 D3 (one notice to the delegate per request and a confirmation) implementation_evidence: observed inference: [] source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f implements: - CAP-PFM-ELG-014 - CAP-PFM-ELG-017 moves: - STATE-PFM-ELG-006 crosses: - SVC-PFM-ELG-responsibilities - SVC-PFM-ELG-attention idempotency: >- Creation has no replay key and a retry can create additional cover rows. Ending rejects arrangements already stored ended. concurrency: >- Single creation locks its holding. Bulk creation is atomic across its selected holdings, without a separately asserted lock on every holding. hops: - 'n': 1 actor_or_service: Delegation operation action: >- Require delegate-own authority for personal delegation or management authority for someone else. anchor: >- services-platform:modules/responsibilities/aws/api/responsibilities.routes.ts:responsibilitiesRoutes seam: sync on_failure: Read permission alone cannot create cover. left_inconsistent: No cover is created by an unauthorized request. observer: The person requesting cover receives the refusal. provenance: observed source: >- services-platform:modules/responsibilities/aws/api/responsibilities.routes.ts:responsibilitiesRoutes - 'n': 2 actor_or_service: Responsibilities persistence (one transaction) action: >- Check an active colleague of the same customer and a one-hour to ninety-day window bounded by each holding end; insert arrangements and transactional notices for both parties. anchor: >- services-platform:modules/responsibilities/services/persistence/delegations.ts:delegateAllMine seam: sync on_failure: Any invalid selected holding or window refuses the bulk transaction. left_inconsistent: No partial set of arrangements or notices commits. observer: The requester sees the validation result. provenance: observed source: >- services-platform:modules/responsibilities/services/persistence/delegations.ts:createDelegation - 'n': 3 actor_or_service: Notifications dispatcher action: Let Notifications deliver the committed cover notices after dispatch. anchor: >- services-platform:modules/responsibilities/services/notices/responsibility-notices.ts:noticeDelegated seam: queue on_failure: Notifications owns delivery retry. left_inconsistent: The colleague can learn about cover later than its start. observer: Notification history exposes delivery. provenance: observed source: >- services-platform:modules/responsibilities/services/notices/responsibility-notices.ts:noticeDelegated - 'n': 4 actor_or_service: Attention read and Home action: >- Resolve effective cover at attention read and show the named cover banner on Home. anchor: >- services-platform:modules/attention/services/read/attention-for-viewer.ts:readViewerSummary seam: sync on_failure: Holder resolution determines visibility on each read. left_inconsistent: Ending or effective expiry removes coverage on a subsequent read. observer: The colleague sees the audience explanation and banner. provenance: observed source: 'react-console:components/responsibilities/covering-banner.tsx' - 'n': 5 actor_or_service: 'Holder, colleague or manager' action: >- End cover as its holder, colleague or manager; ordinary manual holding ending also ends attached cover. anchor: >- services-platform:modules/responsibilities/services/persistence/delegations.ts:endDelegation seam: sync on_failure: >- Unauthorized or stored-ended arrangements are refused; temporal expiry alone does not imply stored ended. left_inconsistent: >- Derived synchronization can leave stored cover rows active but ineffective. observer: The ending caller sees the outcome. provenance: observed source: >- services-platform:modules/responsibilities/services/persistence/delegations.ts:endDelegation branches: - >- Creation uses stored-active status and does not restrict the cover start to the underlying holding start. waits: [] evidence: - >- services-platform at ad3f6a6: modules/responsibilities/services/persistence/delegations.ts; services/notices/responsibility-notices.ts; aws/api/responsibilities.routes.ts; modules/attention/services/read/attention-for-viewer.ts; docs/responsibilities.md §5, §8. - >- react-console at baf6dae: components/responsibilities/my-responsibilities.tsx, covering-banner.tsx, responsibility-dialogs.tsx. controls: [TC-AVL-004, TC-AVL-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-AZ-005, TC-AZ-006, TC-CRY-001, TC-CRY-002, TC-CRY-003, TC-CRY-004, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-IAM-001, TC-IAM-002, TC-IAM-003, TC-IAM-004, TC-IAM-005, TC-IAM-006, TC-LOG-001, TC-LOG-002, TC-LOG-003, TC-LOG-004, TC-LOG-005, TC-MON-001, TC-MON-002, TC-PI-001, TC-PI-002, TC-PI-003, TC-PI-004, TC-PI-005, TC-PRV-001, TC-PRV-002, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-VEN-001, TC-VEN-002, TC-VEN-003] --- # Hand responsibility cover to a colleague ## What It Does A holder or manager arranges temporary cover for personal holdings, or an authorized party ends that cover. ## The Flow ```mermaid flowchart TD H1["Delegation operation" ] H2["Responsibilities persistence (one transaction)" ] H1 --> H2 H3["Notifications dispatcher" ] H2 --> H3 H4["Attention read and Home" ] H3 --> H4 H5["Holder, colleague or manager" ] H4 --> H5 ``` Require delegate-own authority for personal delegation or management authority for someone else. Check an active colleague of the same customer and a one-hour to ninety-day window bounded by each holding end; insert arrangements and transactional notices for both parties. Let Notifications deliver the committed cover notices after dispatch. Resolve effective cover at attention read and show the named cover banner on Home. End cover as its holder, colleague or manager; ordinary manual holding ending also ends attached cover. ## When Something Fails Read permission alone cannot create cover. No cover is created by an unauthorized request. Any invalid selected holding or window refuses the bulk transaction. No partial set of arrangements or notices commits. Notifications owns delivery retry. The colleague can learn about cover later than its start. Holder resolution determines visibility on each read. Ending or effective expiry removes coverage on a subsequent read. Unauthorized or stored-ended arrangements are refused; temporal expiry alone does not imply stored ended. Derived synchronization can leave stored cover rows active but ineffective. ## Open Design Questions Creation uses stored-active status and does not restrict the cover start to the underlying holding start.