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.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Calendar-aware overdue classificationAudience aligned with task routingAttention resolved when work no longer qualifies
Surfaces: consolejob
Preconditions: Attention publishing is enabled for the execution.
Intent sources: services-crm:docs/attention.md#2. Attention definitions

Controls

18 controls apply, from the corpus control catalogue.

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

Business Rules

8 rules, 7 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	An open task becomes overdue when its due day precedes today in the workspace calendar, so work due today is not yet overdue. no proof recorded yet	calculation	service	test 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
`02`must prove Proposed	An overdue item addresses the holder, otherwise the responsibility for its queue, otherwise workspace administrators. no proof recorded yet	policy	service	test 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
`03`must prove Proposed	A task write that leaves work overdue republishes its attention item within the same transaction, updating audience and details. no proof recorded yet	policy	service	test 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
`04`must prove Proposed	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. no proof recorded yet	lifecycle	service	test services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#resolves the item completed when the overdue task is completed
`05`must prove Proposed	The daily sweep publishes overlooked overdue work and resolves attention items whose tasks no longer qualify. no proof recorded yet	lifecycle	service	test 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
`06`must prove Proposed	Rolling back a task write also rolls back its attention changes. no proof recorded yet	invariant	service	test services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#leaves no item behind a task write that rolled back
`07` Proposed	An overdue item carries the title, due day, priority and contact name without granting task access.	policy	service	documented services-crm:docs/attention.md#2. Attention definitions
`08`must prove Proposed	The pinned attention record describes publishing disabled by default pending Platform readiness, without verifying current deployment settings. no proof recorded yet	policy	service	documented services-crm:docs/attention.md#3. The switch

Scenarios

Id	Given	When	Then	Provenance
`01`	Publishing is enabled and a held task is already overdue.	Run the overdue sweep.	The emitted item addresses its holder; Home delivery remains outside this service proof.	test 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	Given	When	Then	Provenance
`02`	A previously overdue task has been completed.	Reopen it while its due day remains past.	An overdue attention item is published again.	test 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

Planning

Route overdue work to the people responsible for it ​

Purpose ​

How It Works ​

Relationships ​