Queue

The Operator Queue: approvals, manual steps, and spot-checks waiting on a human.

The Queue (/admin/queue) is where human work lives. It has three tabs:

Approvals

L2 steps whose automated output is ready for a human decision. Open a row to review the output, then approve or reject it. Approving lets the run continue.

Manual steps

L3 steps that must be done by hand, like "Send offer" or "Gather target". These open on the run page where you fill in the required input.

Spot checks

A sample of L1 (autonomous) outputs routed back for after-the-fact review. You can approve or reject them right in the queue.

Spot checks only exist for promoted L1 steps that also set a positive spot_check_rate — promotion alone is not enough, and no shipped workflow does either today, so this tab is empty on live runs. Seeded demo data can populate it. See Promotion & drift.
Each tab shows a count badge so you can see at a glance how much is waiting on a human.

Why the queue matters

The queue is the human-in-the-loop boundary. Autonomous steps run freely, but anything that needs judgement, such as a draft offer or a verified fact, stops here until a person signs off.