How triage helps

When a Pulse arrives, Exhale prepares a short note for whoever is on call: what fired, a first check, and — when you have connected them — excerpts from your own tools. You can read it, copy a step into Next steps, or leave it. Nothing in triage changes the vendor incident for you.

What triage reads

• The scrubbed Pulse payload (secrets and tenant redaction rules already applied).
• Optional Context from connectors you marked configured: repositories, runbooks, observability, and open Jira or Linear issues.
• A short briefing Exhale builds itself: similar Pulses that already resolved, including steps that helped and ones marked not helpful.

Send-test-alert Pulses skip live collectors and use the built-in stub, even when a model is configured.

What stays out of the model

Raw webhook bodies are not logged. Tenant scrub rules run again on Context excerpts before they are stored or sent. A connector that is still pending, in error, or opted out is not queried. If a collector times out or the vendor declines the token, that block is skipped and triage still finishes.

The JSON shape of the reply is fixed by the platform. Custom instructions can change tone. They do not change the schema or the safety rules.

What you see

On the Pulse, Triage → Results shows the summary, recommended checks, and — when you have turned it on — confidence. What informed this names the excerpts the model actually cited. Those citations are kept only when the label matches an excerpt that was attached. Triage → Context holds the excerpts themselves, including open issues and status-page incidents.

The Pulse list can show a quiet line for the week: how many Pulses received guidance, how quickly that usually happened, and how many related alerts were grouped. Reports repeats that summary. Send-test-alert Pulses are left out of that line and out of the Reports summary. The minutes figure is an estimate (about eight minutes of orientation per guided Pulse), labeled as such.

GET /v1/reports/impact?window_days=7|30 returns the same numbers for every plan. Viewers can read it.

How Context changes the pass

Without Context, triage works from the payload and from similar Pulses already in the workspace. With Context, the first check can point at a commit, a runbook section, a log line, an open issue, or a status-page incident you already published. You choose what to connect, and you can opt a connector out of the prompt without disconnecting it.