Escalation Policy
When an event stalls, the cockpit escalates on a fixed clock. Each rung pages a wider circle and ratchets the severity floor upward — an item that lingers can only get more severe, never less. Two clocks share the same rungs: a relaxed planning clock and a compressed clock for live events.
Escalation Timeline
Each rung fires at T+nn minutes after the stall begins. Bar position tracks the rung against the last rung on this clock.
Nudge the owner: re-surface the stalled item at the top of their queue.
Page the area lead and open a tracked escalation thread alongside the owner.
Declare an incident: hand to the on-call commander and freeze dependent transitions.
Severity-Upgrade Rules
Severity is monotonic — it only ratchets upward as the clock runs. Each rule states a trigger and the severity floor it guarantees.
Stall is newly detected (before the first rung fires)
InfoFirst rung crossed without resolution
InfoSecond rung crossed, or the item already carries a Warning
WarningThird rung crossed, an incident is declared, or a dependent transition is blocked
CriticalOnce the ladder fully runs, the item is pinned at Critical until a human resolves the stall.
Escalation policy is illustrative cockpit project-tracking state authored in src/data/escalation-policy, not product data. The same rungs drive both clocks; the LIVE clock simply compresses the offsets.