Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaInitiative status vs Queue-row statusGuide page

Initiative status vs Queue-row status

Concept a word Carolverse uses with a precise meaning

📖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.

⚖️What it is NOT

The neighbours this word is most often confused with, and the line between them.

Not: Dispatch queue row

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.

🧭The 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

statusqueue status

🔗Related ideas

Status routerDispatch queueParkedBlocked