Software has fuzzing.
Operating procedures have nothing.

Every plant runs the same ceremony: a hazard review, a written procedure, a signature, and then a tired person at 3am doing it anyway. Nobody tests the procedure. MURPHY does what developers have done to code for forty years - it throws a few thousand error-prone crews at the written sequence, against a physics twin of the equipment, and reports which station the line fails at, how much the company pays for it a year, and which change would measurably fix it.

3 controlled procedures, 50 steps, 11 plant states, 6 crews, 12 candidate controls. It runs in this browser; the same kernel is written to run batched on an AMD Instinct device, and the chip above says which machine answered - it has never shown a device it does not have.