Plain-English Summaries (AI)

Where you'll see them

Three surfaces carry an AI-written explanation, each marked with an AI summary badge:

• Alert briefs. Every alert detail page opens with "What happened, in plain English": a few sentences saying what tripped, why it matters for a storefront, and what to look at first. Written for the whole team, not just the person who knows what a 499 ratio is.
• Rule notes. When an alert carries a drafted eCDN rule, a note beneath it explains in plain terms what the rule will and will not affect: which traffic gets challenged, who is untouched, and what to watch after applying.
• Weekly digest. The "Your week in traffic" section on the Overview opens with a short narrative of what changed this week and whether anything needs attention. See Your Week in Traffic.

What the AI does and does not control

The division of labour is strict, and it is the whole point:

• The numbers come from the deterministic pipeline. Every figure in a summary is computed by the same queries that power the page you are looking at. The AI is given those numbers and writes sentences around them; it does not calculate, estimate, or invent anything.
• Drafted rules are never AI-generated. The rule expression on an alert is built by fixed logic from the alert's own evidence. The AI only describes it.
• Summaries are display-only. Nothing an AI writes feeds a detector, changes a threshold, or triggers an action. Nothing is ever applied to your storefront without a person clicking Apply.

Each summary card carries this caption so nobody has to take it on trust.

The daily allowance

Summaries have a fair-use daily allowance per workspace. Once it is used up, the cards say so and summaries resume the next day. Everything else on the page (the data, the drafted rule, the playbook) is unaffected; only the prose pauses.

Summaries are also cached: revisiting the same alert reuses the existing brief rather than generating a new one, so the allowance goes a long way in normal use.

When a summary doesn't appear

If a summary is unavailable (allowance used up, or the summary service is briefly unreachable), the card either explains why or simply doesn't render. Nothing about detection, alerting, or guided response depends on it.