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.