--- id: CAP-CRM-ACT-015 title: Route overdue work to the people responsible for it feature: FEAT-CRM-ACT-03 product_area: crm module: activities-tasks revision: 2 status: draft product_intent: proposed implementation_evidence: partially-observed supersedes: - react-console acceptance inventory CAP-CRM-ACT-020 source_sha: services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f intent_sources: - 'services-crm:docs/attention.md#2. Attention definitions' purpose: Overdue task attention helps responsible staff notice work that has slipped. outcomes: - Calendar-aware overdue classification - Audience aligned with task routing - Attention resolved when work no longer qualifies concepts: - CON-CRM-ACT-003 actors: - ACT-CRM-003 - ACT-CRM-005 - ACT-CRM-006 surfaces: - console - job preconditions: - Attention publishing is enabled for the execution. postconditions: [] permissions: [] rules: - id: BR-CAP-CRM-ACT-015-01 proved_by: [ATS-CRM-ACT-014-05, ATS-CRM-ACT-015-01, TST-CRM-ACT-018, TST-CRM-ACT-019] statement: >- An open task becomes overdue when its due day precedes today in the workspace calendar, so work due today is not yet overdue. kind: calculation enforced_at: - service must_prove: true provenance: test source: >- services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#publishes nothing for a task due today, which is not overdue until the day ends origin: none - id: BR-CAP-CRM-ACT-015-02 proved_by: [ATS-CRM-ACT-012-10, ATS-CRM-ACT-015-02, TST-CRM-ACT-018] statement: >- An overdue item addresses the holder, otherwise the responsibility for its queue, otherwise workspace administrators. kind: policy enforced_at: - service must_prove: true provenance: test source: >- services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#addresses a queued task nobody holds to the task queue responsibility at its queue origin: none - id: BR-CAP-CRM-ACT-015-03 proved_by: [ATS-CRM-ACT-015-03, ATS-CRM-ACT-015-07, TST-CRM-ACT-018] statement: >- A task write that leaves work overdue republishes its attention item within the same transaction, updating audience and details. kind: policy enforced_at: - service must_prove: true provenance: test source: >- services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#moves the item to the new holder when an overdue task is assigned, in the same generation origin: none - id: BR-CAP-CRM-ACT-015-04 proved_by: [ATS-CRM-ACT-011-09, ATS-CRM-ACT-015-04, ATS-CRM-ACT-015-07, TST-CRM-ACT-018] statement: >- Closing, deleting or moving an overdue task’s due day to today or later resolves its attention item in the same transaction with the corresponding reason. kind: lifecycle enforced_at: - service must_prove: true provenance: test source: >- services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#resolves the item completed when the overdue task is completed origin: none - id: BR-CAP-CRM-ACT-015-05 proved_by: [ATS-CRM-ACT-015-05, TST-CRM-ACT-018] statement: >- The daily sweep publishes overlooked overdue work and resolves attention items whose tasks no longer qualify. kind: lifecycle enforced_at: - service must_prove: true provenance: test source: >- services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#publishes the overdue task no write had published, with no contact origin: none - id: BR-CAP-CRM-ACT-015-06 proved_by: [ATS-CRM-ACT-015-14, TST-CRM-ACT-018] statement: Rolling back a task write also rolls back its attention changes. kind: invariant enforced_at: - service must_prove: true provenance: test source: >- services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#leaves no item behind a task write that rolled back origin: none - id: BR-CAP-CRM-ACT-015-07 proved_by: [] statement: >- An overdue item carries the title, due day, priority and contact name without granting task access. kind: policy enforced_at: - service must_prove: false provenance: documented source: 'services-crm:docs/attention.md#2. Attention definitions' origin: none - id: BR-CAP-CRM-ACT-015-08 proved_by: [ATS-CRM-ACT-015-06] statement: >- The pinned attention record describes publishing disabled by default pending Platform readiness, without verifying current deployment settings. kind: policy enforced_at: - service must_prove: true provenance: documented source: 'services-crm:docs/attention.md#3. The switch' origin: none note: >- The record describes default switches and prerequisites without observing live deployment. scenarios: - id: SC-CAP-CRM-ACT-015-01 given: Publishing is enabled and a held task is already overdue. when: Run the overdue sweep. then: >- The emitted item addresses its holder; Home delivery remains outside this service proof. provenance: test source: >- services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#publishes the overdue task no write had published, with no contact edge_cases: - id: SC-CAP-CRM-ACT-015-02 given: A previously overdue task has been completed. when: Reopen it while its due day remains past. then: An overdue attention item is published again. provenance: test source: >- services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#opens a second generation when a completed overdue task is reopened constraints: [] depends_on: - CAP-CRM-ACT-011 - CAP-CRM-ACT-012 related: - CAP-CRM-ACT-014 journeys: - JNY-CRM-ACT-003 open_questions: - OQ-CRM-ACT-002 evidence: - >- services-crm at a8d1364f1dd44b723bb5f9acba12f983e9ec8d69: Independently reviewed declarations, behavior and assertions identified in this capability’s row citations. controls: [TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-IAM-001, TC-IAM-005, TC-IAM-006, TC-LOG-005, TC-MON-001, TC-MON-002, TC-PI-001, TC-PI-002, TC-PI-004, TC-PI-005, TC-PRV-001, TC-PRV-002, TC-TEN-001, TC-TEN-002, TC-TEN-003] exercised_by: [FAS-CRM-ACT-03-02, FAS-CRM-ACT-03-06] suites: [TST-CRM-ACT-018, TST-CRM-ACT-019] --- # Route overdue work to the people responsible for it ## Purpose Overdue task attention helps responsible staff notice work that has slipped. ## How It Works Rhythm compares open tasks with the workspace’s current day. An overdue task produces an attention item for its holder or the appropriate shared audience. Task writes keep that item aligned within their own transaction. Completing, cancelling, deleting or rescheduling work can resolve it. A daily sweep catches tasks that became overdue without another edit. The item provides task context but grants no additional permission. The integration record describes attention publishing disabled by default until Platform is ready. This examination does not establish a live switch setting or Home delivery. The product should verify registration and publishing before relying on reminders operationally. ## Relationships - Task assignment determines the current audience. - Task lifecycle and date changes remove overdue conditions. - Platform attention and responsibilities own delivery and responsibility resolution.