# Store Monitoring Signal Catalog

Companion to **Stop Asking Dashboards Questions: Let AI Agents Monitor Your Store**.

The daily brief ([`operations-daily-brief-schema.md`](operations-daily-brief-schema.md)) is a **scheduled JSON**. This catalog is **always-on signals** → detect → investigate → recommend.

```text
Business Signals → AI Monitoring → Problem Detection → Investigation → Recommendation → Human / Automation
```

## Signals (name tools; replace thresholds)

| Domain | Example signal | Detect (code) | Investigate (agent) |
| ------ | -------------- | ------------- | ------------------- |
| Sales | Revenue vs trailing 7d | Threshold | RCA hops if needed |
| Orders | Exception queue depth | Count | Exception pattern |
| Inventory | ATP=0 on advertised SKU | Join ads + ATP | Confirm `asOf` |
| Customers | Duplicate create spike | Rule | Data quality |
| Support | Tag volume spike | Count | Theme — not invented UX |
| Returns | RMA rate vs baseline | Rate | Refund matrix / quality |
| Marketing | Spend with ATP=0 | Join | Pause **recommend** |
| Fulfillment | SLA breach | WMS/3PL | Exception agent |

Human-opens-dashboard is the **reactive** model. This is the **proactive** model. Cap pages to humans; overflow is a watch list.

## Related

- Daily brief: [`operations-daily-brief-schema.md`](operations-daily-brief-schema.md)
- Exception pattern: [`exception-agent-pattern.md`](exception-agent-pattern.md)
- Alerts: [`evidence-based-alert-schema.md`](evidence-based-alert-schema.md)
- Control tower: [`operations-control-tower-architecture.md`](operations-control-tower-architecture.md)