# Escalation Rules

Escalation transfers a decision to the correct authority with enough evidence to decide. It is not a vague request for help.

[Team README](README.md) · [Roles](Team%20Roles.md) · [Workflow](Team%20Workflow.md) · [Master Team Prompt](Master%20Team%20Prompt.md) · [Quality Checklist](Team%20Quality%20Checklist.md)

## Escalation Levels

| Level | Trigger | Recipient | Required Package |
| --- | --- | --- | --- |
| Agent-to-agent | Missing specialist input or contract mismatch | Named specialist | Task, evidence, exact question |
| Orchestrator | Dependency, conflict, ownership, or loop problem | Orchestrator | Options, trade-offs, recommendation |
| Human approval | Scope, cost, sensitive, public, destructive, legal, production, or authority decision | [HUMAN APPROVER] | Intended effect, risk, rollback, choices |
| Critical stop | Protected data, unauthorized action, invalid final result, or unsafe continuation | Human + team stop | Preserved evidence, affected scope, containment |

## Escalation Format

~~~markdown
# Escalation
Decision needed: [ONE QUESTION]
Why now: [TRIGGER]
Evidence: [REFERENCES]
Affected tasks/files/users: [SCOPE]
Options: [A/B/C]
Trade-offs: [EFFECTS]
Recommended option: [CHOICE + REASON]
Deadline/impact: [WHEN/WHAT]
Safe state while waiting: [PAUSED/PRESERVED]
~~~

Escalate immediately when unresolved unclear positioning, broken mobile navigation, silent form failure can cross the approved risk threshold.

## Decision Tests

Before escalating, confirm that the issue cannot be resolved inside the current task contract and permission. The receiving authority should be able to decide whether to preserve, revise, narrow, pause, or stop the work. For this team, explain how each option affects communicate the offer within ten seconds and reach primary content in two navigation decisions. Keep the project in a safe, recoverable state while waiting and do not let other agents bypass the pending decision.