---
id: ADR-CRM-ACT-010
title: Overdue attention shares task transactions and uses conditional daily reconciliation
product_area: crm
module: activities-tasks
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Synchronize enabled overdue attention within task persistence and supplement it with
  daily reconciliation, retaining the default-off switch required by the recorded
  deployment-order rule.
constrains:
  - DOM-CRM-ACT-003
  - STATE-CRM-ACT-004
  - SVC-CRM-ACT-tasks
  - WF-CRM-ACT-003
  - WF-CRM-ACT-006
origin: >-
  The Work Coordinator's deploy-order rule (Andrew, 2026-10-18), recorded at services-crm
  docs/attention.md §3 and lib/attention.ts; Platform attention design 05 §3.3 as cited
  there.
alternatives:
  - option: Publish task attention through a post-commit change reaction.
    why_not: >-
      Tasks have no registered change stream, and this alternative would require a new
      delayed-publication contract.
  - option: Publish overdue work only in the daily sweep.
    why_not: >-
      Routing changes could remain undiscovered until a later pass rather than updating
      with persistence.
  - option: Enable attention publication in every deployment by default.
    why_not: >-
      The cited deployment-order rule avoids calling Platform dependencies before they are
      available.
consequences:
  - >-
    A task’s own attention changes share its transaction when enabled; direct reference
    changes and reconciliation races can leave older item details.
  - >-
    A publication error can prevent the task change from committing, retaining the
    recorded availability question.
  - >-
    Daily scheduling delays discovery after a due day ends, and failed or deferred passes
    can extend that delay beyond a day.
  - >-
    Disabled publication leaves overdue discovery in console views and preserves any
    previously existing items.
supersedes: []
evidence:
  - >-
    services-crm at a8d1364f: lib/attention.ts;
    modules/tasks/services/persistence/task-attention-items.ts; aws/crm.attention.ts;
    aws/crm.attention-sweeps.ts; docs/attention.md §3 to §5.
---

# Overdue attention shares task transactions and uses conditional daily reconciliation

## Context

Overdue work needs an audience and timely discovery. Its publication also introduces a dependency into otherwise local task writes.

## Decision

The cited switch decision governs deployment order. Local persistence publishes or resolves qualifying work in its own transaction, while the daily function attempts reconciliation from separately read pages. This establishes transactional coupling rather than exact ongoing item freshness.

## Alternatives Considered

The structured alternatives describe concrete competing designs and their tradeoffs. Where the origin records an existing ruling, it remains the authority; an observed implementation does not establish Product’s rejection of every alternative.

## Consequences

Activation depends on an ordered deployment decision and external readiness evidence. Product must settle publication failure policy and acceptable stale-item or discovery delay.