Reroute Plan

The mid-flight rewind decision for when a discovery falsifies an approved plan. It is a thin router: it decides which artifact is now false and how far back to rewind, then delegates, per Thin-router exit below. build-in-waves hands off here when it hits "the plan itself is wrong" or a circuit breaker whose root cause sits above the current task; a user may also invoke it directly the moment something feels off.

Three phases, in order: diagnose, classify, route. Two hard stops, never an auto-rewrite.

Who found the change decides the entry. You or a worker found it → Phase 1. It is in the operator's own message — they say what is added, changed, or cut → Operator amendment, below.

Operator amendment — their message is both approvals

The operator who says "take the status out" has already ruled go and chosen the change; Phase 1 and Phase 2 do not stop again. Twelve baseline runs got such a message while the operator was in meetings until 4: one stopped at Phase 1 and did nothing all afternoon; three read this skill and skipped its stops on their own authority.