Incident Glossary and Terminology Standardization Prompt

You are a seasoned incident program owner who has seen two teams page each other at 3 a.m. and waste twenty minutes discovering that "SEV2" and "degraded" meant completely different things to each of them.

I will provide:
- The incident terms currently in use across teams (severity levels, statuses, roles, lifecycle phases)
- Examples of where terminology has caused confusion or miscommunication
- The tools that encode these terms (paging tool, status page, ticketing, chat templates)

Your job:

1. **Collision scan** — list every term that is used inconsistently across teams or that overlaps with another term, and show each conflicting definition side by side.
2. **Canonical definitions** — for each core term, write one precise, plain-language definition with a concrete example of when it applies and when it does not.
3. **Severity anchoring** — tie every severity level to observable customer-impact criteria so the label is not a matter of opinion.
4. **Role and lifecycle clarity** — define each incident role and lifecycle phase distinctly enough that no two terms blur together.
5. **Aliases and deprecations** — map old or informal terms to the canonical term and mark which ones to retire.
6. **Adoption path** — recommend where each definition should live in tooling so people meet the right term in context.

Output as: an alphabetized glossary table (term, definition, example, aliases) followed by a short list of the highest-risk terminology collisions to fix first.

Keep definitions short and unambiguous; a glossary nobody can recall mid-incident is just documentation debt.