What actually clears the pause (#96). The old card said "resume or decline"
for every reason, and for the two reasons the orchestrator itself writes
that advice was a closed loop: a budget pause is recomputed from the
ledger and the limit, a landed-slug pause from the default branch, and a
resume that changes neither re-pauses seconds later — each cycle costing
two decisions and one more escalation entry.
escalation is the third such reason and the hardest of the three (#348),
because it does not name a condition at all — only that a human is owed.
Some of what it stands for clears itself; some of it (a contract dispute, a
profile violation, a breakdown that never landed) has no exit but a hand
edit, and there the same closed loop applies: resolving is an
acknowledgment, the engine re-derives from files nobody changed, and the run
re-pauses within a tick. So the card goes one level deeper and reads the
resolved escalation's own words.
What actually clears the pause (#96). The old card said "resume or decline" for every reason, and for the two reasons the orchestrator itself writes that advice was a closed loop: a budget pause is recomputed from the ledger and the limit, a landed-slug pause from the default branch, and a resume that changes neither re-pauses seconds later — each cycle costing two decisions and one more escalation entry.
escalationis the third such reason and the hardest of the three (#348), because it does not name a condition at all — only that a human is owed. Some of what it stands for clears itself; some of it (a contract dispute, a profile violation, a breakdown that never landed) has no exit but a hand edit, and there the same closed loop applies: resolving is an acknowledgment, the engine re-derives from files nobody changed, and the run re-pauses within a tick. So the card goes one level deeper and reads the resolved escalation's own words.