📖What it means

Two state machines that must never be conflated. INITIATIVE STATUS is the lifecycle state of the initiative record itself (filed → planned → active/executing → blocked/diagnosis → reviewing → uat-pending → closed), owned by the status router — it says where the WORK stands. QUEUE-ROW STATUS is the state of a dispatch-queue row — transport bookkeeping that says whether an execution slot has been requested, picked up, or needs attention. A queue row is not the initiative: an initiative can legitimately be executing with no queue row (the backlog is intentionally card-less), and a missing queue row is not evidence the initiative is stuck. Deriving one status from the other is the root of past phantom-block incidents.

📖Easily confused with

[{"term": "Dispatch queue row", "distinction": "The initiative's status is the work's lifecycle; the queue row's status is only that row's place in the dispatch line. Conflating them is how work gets stranded."}]

📖Nuance

Carol: status changes go through Elrond's status router (never raw UPDATEs); blocked→dispatched is a forbidden transition; the dispatch queue is hard-capped and its rows are written in-transaction by the router (single source of truth).

📖Also called

- status
- queue status

📖Filed under

Category: work.

Service: Build Initiatives.