Written down isn't the same as known.

A work instruction carries the procedure. It doesn't carry the judgment that goes with it, and that sits with a few veteran operators who eventually retire.

One of us spent a year on an aerospace production floor, running root cause on non-conformance material and unblocking operators. The other builds an enterprise data-validation system that catches bad values before they reach a customer's account. OperBot sits where those two jobs meet.