Triage a change

You opened a change card — from a Slack alert, a PagerDuty page, or the in-app inbox. This page is what to do next.

The 30-second read

Every change card has the same shape. Read it top to bottom and you'll know what you need to know:

1. The headline. "Stripe removed customer.email_verified from GET /customers/:id." Severity is the chip on the right.
2. The diff. Side-by-side before/after of the affected piece of the spec. No prose commentary — just what changed.
3. What we think it touches in your code. Based on your domain mappings (see below). If you haven't set those up yet, this section says so.
4. History. Has this endpoint changed before? Same vendor? Same field? Useful when the same area keeps moving.
5. Actions. Acknowledge, assign, resolve, comment.

If you understand the headline and the diff, you have what you need to decide. The other sections exist to speed up the decision, not to be read every time.

What "it touches in your code" actually means

Intello doesn't read your code. It reads the domain mappings you set up — a list of which of your services use which endpoints — and uses those to tell you what's likely affected.

If you haven't set up mappings, the change card still works; it just can't connect the dots. We cover mappings on Domain mapping & impact.

Decide one of three things

Every change boils down to one of:

• No action needed. Most Safe changes. Mark resolved.
• Heads-up, no work yet. A deprecation announced for six months out, a tightening that doesn't affect your usage. Acknowledge and assign to the relevant team if needed.
• Real work. Code update, version bump, schema migration. Acknowledge, assign, link the resulting PR/ticket in the comment field, mark resolved when shipped.

That third path is where Intello earns its keep. The other two are about not being surprised.

When the change is wrong

Sometimes Intello flags something that isn't really a change — a vendor restructured their spec without changing behavior, or moved a field between two equivalent locations. You can mark a change as Not a real change at the bottom of the card. We use that signal to improve the diff engine for your org.