Command Center is the daily starting point for AI OS work. It collects the work Vertiqa believes needs attention: approvals, commitments, customer follow-up, blocked work, alert rule signals, and agent runs that failed or stalled.
Use it when you want to answer: "What needs a decision from me now?"
Business-first item rows
Each Command Center item is presented in a business-first layout:
- Business object — the customer, account, deal, job, or estimate that needs attention. Never a raw ID.
- Risk summary — what is at risk in business terms: a stale quote, a missed follow-up, an overdue task, a blocked job.
- Promise, deadline, or blocker — when the commitment was made or when the risk becomes critical.
- Recommended action — what to do next: approve draft, close commitment, retry run, snooze item.
- Evidence summary — the key signal that surfaced the item: last contact date, deal stage, cost vs. ceiling, technician update.
Raw scores, policy decision IDs, source names, and loop mechanics are secondary detail — available in expandable rows, the Run Inspector, and AI OS Activity & Health, but not as primary copy.
First pass workflow
- Open Command Center from Full mode, or Queue from Simple mode.
- Start with the highest-priority item at the top.
- Read the business object and risk summary to understand what is at risk.
- Check the evidence summary to confirm the item is based on real operating data.
- Take the inline action only if the recommendation matches what you would do manually.
- If the item is real but not urgent, snooze it.
- If the item is not useful, dismiss it with a reason.
The queue should become smaller as decisions are made. If an item remains after an action, refresh the page and check whether the underlying record still meets the queue condition.
Drafts are reviewable — no autonomous external send
When an AI loop proposes an action (draft email, task creation, record update), it appears in the Approval queue as a draft for operator review. External send remains human-triggered. You review the draft, check the dry-run before/after diff if shown, and approve or reject. Nothing is sent without your action.
Common actions
- Approve draft — review and approve a proposed action. The before/after diff shows exactly what will change.
- Close commitment — mark a promised follow-up or obligation as fulfilled.
- Retry run — queue a failed agent run again after checking the failure context.
- Cancel run — stop a queued or running agent run that should not continue.
- Snooze — hide a valid item until a later review window.
- Dismiss — remove an item that is not actionable or no longer relevant.
When to open another surface
Open AI OS Activity & Health at /ai-os when the question is not
about a single item but about which loops are active, what guardrails and
usage limits are in place, or what overall loop health looks like.
Open Recent activity (via AI OS Activity & Health) when the item is about a failed, stuck, retried, or cancelled agent run.
Open Alert rules (via AI OS Activity & Health) when the item is about a rule, alert, or actual-vs-intended mismatch.
Open Guardrails, Usage limits, or Recurring checks (via the AI OS Activity & Health overview) when the issue is not a single queue item but how agent loops are allowed to run, how often, and within what limits.
Simple mode
Simple mode shows the same underlying queue through Queue. Use it for mobile triage and daily operator work. It intentionally hides most setup and configuration, but the actions still go through the same governed Kernel APIs.