Decision queue

The Decision queue is the primary attention surface on Command center. Instead of scanning dozens of metrics, you see a short list of prioritized decisions — up to five — each with enough context to act.

What each card shows

• What happened — the insight title (or a Margin Keep finding title when Margin Keep is installed)
• Why it matters — root-cause headline or summary
• Estimated impact — dollar estimate when Revenue at risk applies (Growth+), or Margin Keep’s estimated margin impact
• Recommended action — install an Engine playbook, review manually, or open the Margin Keep ledger
• Engine can act vs Manual review — whether a mapped playbook exists
• Owner — suggested team role (Inventory, Marketing, Merchandising, or Ops), or Margin Keep for margin findings

How priority works

Sentinel ranks open insights by severity (Critical first), then by estimated impact when available. Recent Margin Keep findings, when that app is installed on the same store, appear in the same short list so contribution-margin risks stay visible alongside operational insights. Only the top five appear in the Decision queue. Full detail remains on Insights (and in Margin Keep’s ledger for margin findings).

Margin Keep findings

When Margin Keep is installed, contribution-margin risks it detects (for example a floor breach on a promotion) can show up in the Decision queue with owner Margin Keep and a manual action to open the Margin Keep ledger. Sentinel does not change Margin Keep settings or pause discounts for you — use Margin Keep for that.

Engine handoff

When a decision shows Engine can act, Install in Engine (or Open in Engine to install) opens Arcanum Engine with safe defaults for you to confirm. Sentinel never activates a playbook without your confirmation. Hollow Sentinel and Arcanum Engine stay separate apps — you can use either alone.

Engine integration — Detected by Sentinel and confirm-before-activate

Revenue at risk — how impact estimates are built