AI Executive Office — CXO Assistant Platform  ·  View 18 of 30  ·  5 · Runtime

Proactive Intelligence — Signal to Situation

How an exception is found before anyone asks, and why no model is asked to watch the business.

Editable source SVG draw.io All views
Signals KPI refresh gold, hourly Business events Eventstream New documents crawl delta External feeds market · weather Baselines History same period last year Plan and budget committed Peer cohort same BU class Detectors Threshold tenant config Anomaly model Azure ML Forecast deviation actual vs predicted Graph propagation supplier → project Triage Materiality score value × confidence Deduplicate one per root cause Suppression logged · expiring Below the bar recorded, not shown Situation Situation record durable, not a message Root-cause pass agents + graph Impact and forecast deterministic Option set cost · risk · delay Brief Rank for this CXO role + portfolio Teams brief card 07:10 local Executive home Today view below threshold opens the record Proactive Intelligence — Signal to Situation Data store Queue / topic External / third party Application we own Decision point Security / platform Risk / gap Interface / broker failure / alternate synchronous Detection is deterministic and runs on a schedule. No model is asked to watch the business; models narrate a signal that a detector already raised. v 1.0 · owner Data & AI Global Practice · date 2026-09

Decisions

  • Detection is deterministic and scheduled: thresholds, anomaly models, forecast deviation and graph propagation. Models narrate a signal a detector already raised. Asking an LLM to monitor continuously is unaffordable and unrepeatable
  • Graph propagation is what turns a supplier signal into a project exception. It is the capability that answers "which suppliers are affecting projects already at financial risk", and it is why the entity graph exists
  • A situation is a durable record, not a notification. The brief card opens the record; it does not contain it

The hard part

  • Triage, not detection, is what makes this usable. A platform that surfaces forty exceptions has surfaced none. Materiality scoring, deduplication to one item per root cause, and a recorded suppression list are the difference
  • Suppressions expire and are logged. A permanently suppressed alert is a repealed control

Numbers

  • Target: no more than 5 items in a morning brief, and every one actionable
  • Signals below the bar are recorded, not discarded, so a missed exception can be traced to the threshold that hid it
  • Detection sweep hourly; event-triggered for supply-chain and financial-anomaly classes
◀  Who Answers What All views The Closed Loop  ▶
Solution Architecture v1.0 · Azure-native, multi-tenant, sovereign-capable · Data & AI Global Practice · 2026-0918-proactive-detection-pipeline