Escalation Chain
The predefined path that a governance violation or exception follows — from detection through notification, review, and resolution.
An escalation chain is the structured process that activates when an action is blocked by a governance constraint or when an exception requires human judgment.
In human-carried governance, escalation is ad hoc: someone calls someone, sends a Slack message, or sets up a meeting. This is slow, inconsistent, and leaves no record.
In institution-carried governance, escalation is structural: 1. The governance gate detects a constraint violation or boundary case 2. The relevant authority is identified automatically (based on the constraint's scope) 3. A notification is sent with full context (what was attempted, which constraint was triggered, relevant precedents) 4. The authority reviews and decides (approve, deny, or modify the constraint) 5. The decision is recorded as a governance trace 6. If the authority doesn't respond within a defined timeframe, the escalation escalates further
This ensures that governance exceptions are handled consistently, with full evidence, and without depending on informal communication channels.
How Constellation handles this
Constellation automates escalation chains. When the governance gate blocks an action, the system identifies the appropriate authority, sends context-rich notifications, and tracks the resolution.