The Decision Queue

A live command center generates a stream of things that need a human’s attention. An alert fires and creates a notification. An AI agent surfaces a recommendation and asks for sign-off. The agent proposes a governed action and waits for someone to approve it. Each of those lives in its own surface — the Alerts tab, the verification gate inline on a notification, the action approval card. Useful in isolation, but if you walk in fresh and want one place that says “here’s what’s pending,” none of them is it.

The Decision Queue is that one place.

What the queue aggregates

The queue is a single ranked list that pulls together three streams:

• Notifications that haven’t been dismissed.
• Recommendations with a pending verification status — the AI suggested something and is waiting on a human decision.
• Action proposals in any active state — proposed, approved, executing. Once a proposal lands on completed, failed, or rejected it drops off the queue and becomes part of the audit trail instead.

Each entry shows up with a urgency badge, a source badge (which surface produced it), the originating agent or alert, and a deep-link Open button that takes you straight to the underlying card on the Alerts tab and scrolls and pulses it so you can find it instantly even on a busy dashboard.

Filter pills

The top of the queue carries segmented filter pills so you can narrow the view to a single source at a time — alerts only, recommendations only, action proposals only — or stay on All to see everything. The pill counts update live as new items land and old ones resolve.

If a stakeholder walks up and asks “what does this command center need from me right now?”, the queue is the answer. The Alerts tab is still the right place to triage individual alerts in depth; the Decision Queue is the right place to see the whole shape of pending work in one glance.

Open and act in place

Clicking Open on a queue entry doesn’t take you to a separate detail page — it deep-links into the Alerts tab with the matching card scrolled into view and visually highlighted. From there you have everything you’d have if you’d navigated there manually: the full notification with its matched data, the recommendation’s reasoning chain and verification gate, or the action proposal with its parameters, agent reasoning, and approve/reject controls.

The queue is a router, not a workflow surface. Decisions still happen on the Alerts tab and in chat — but you reach them from a single ranked list instead of three separate views.

What’s not on the queue

The Decision Queue is for things waiting on a human. It deliberately does not show:

• Alerts that haven’t fired (those live on the Alerts tab as configurations).
• Notifications you’ve already dismissed (still queryable from the audit log).
• Action proposals that have already terminated — completed, failed, or rejected items move into the audit log and the ledger.
• Long-running scenario or report jobs (those have their own progress affordances).

This keeps the queue focused on action. Everything else has its own home; the queue is the inbox.