Task Overdue Standing

The Lifecycle

Overdue is a calculated condition, and publication is a separate condition. The labels summarize both rather than asserting an exact correspondence between task and attention records. Work due today remains on time until that day ends in the workspace calendar.

Transitions Explained

Enabled persistence writes publish, refresh or resolve attention within their task transaction. A daily pass supplies publication after a deadline passes without a write and resolves older unseen items after completing a workspace. Its separately read pages can race task changes.

What Cannot Happen

The default-off publication switch suppresses attention writes. It does not erase existing items. A task transaction that rolls back also rolls back its own attention changes. Attention supplies discovery rather than authorization to read the underlying task.

Concurrency and Timing

A task can become overdue before its next write or daily pass. A skipped or unsuccessful pass can extend this gap. Reconciliation has a workspace-boundary time budget and no per-task concurrency safeguard, leaving eventual repair without a bounded guarantee.