An action lands in the queue when it needs a person: because the level the agent runs at holds it, because the permission on that action is Ask first, or because it is on the always-asks floor that no level moves. The queue’s home is the Inbox section of the Agents home, and a pending count rides the Agents item in the sidebar so you know when something is waiting.

Nothing in the queue has happened yet. Each item is a proposed change held back until you decide.

• Action: what the agent wants to do, in plain language.
• Affects: the exact record and entity the change would touch.
• Recipients and content: the immutable public envelope for any message or external effect.
• Risk: folded into that consequence sentence as its first word, and only above the low tier, so a consequential change reads differently instead of wearing a badge.
• Run state: the proposal remains valid only while its parent run is active and waiting.

Approve and Reject sit on the row itself, so clearing a queue does not mean opening one panel per item. The row is the third affordance: expand it for Details, or choose Edit before approving to change what would be sent before you agree to it.

Filter by agent to focus on one, by record type to focus on companies or deals, and by risk to triage high-risk items first. A proposal becomes stale if its parent run ends or the original grant, record, recipient, parameters, or authority no longer matches. It must be proposed again before it can run.