Triage a change

When you open a change card — from a Slack alert, a PagerDuty page, or the Incidents view — this is the workflow for deciding what to do next.

The 30-second read

Each change card follows a consistent structure. Reading it top to bottom provides the information needed to make a triage decision:

1. Headline. A one-line summary, for example: "Stripe removed customer.email_verified from GET /customers/:id." The severity badge appears alongside the headline.
2. Diff. A side-by-side comparison of the affected portion of the specification, before and after. The view contains structural changes only; there is no editorial commentary.
3. Affected domain. The API domain Intello inferred for the change — for example, billing or webhooks — derived from the specification's tags and path structure.
4. History. Whether the same endpoint, schema, or field has changed before. Recurring activity in a single area is often a useful signal.
5. Actions. Acknowledge and Resolve, available on the card.

If you understand the headline and the diff, you have enough information to decide. The remaining sections are intended to accelerate the decision rather than to be reviewed every time.

What the affected domain tells you

Intello does not read your application code. Each change is tagged with the API domain it touches — derived automatically from the OpenAPI tags and path structure of the specification — so you can quickly identify which area of your integration is implicated.

For example, a change tagged billing indicates that the affected endpoint is part of the billing surface of the provider's API. To map that domain to the part of your own system that consumes it, see Domain mapping & impact.

Three possible outcomes

Most triage decisions reduce to one of the following:

• No action required. Most Safe changes — additive, backwards-compatible. Resolve the change.
• Awareness only. A deprecation announced for a future release, or a tightening that does not affect your current usage. Acknowledge the change so the team knows it has been seen.
• Code change required. A version bump, schema migration, or client update. Acknowledge the change to claim it, complete the work, and then resolve once the fix has shipped.

The third case is where Intello provides direct value. The first two cases prevent surprises.