That's not very useful though, unless it is predictable and repeatable?

I think that's the argument from some of the other commenters: making it predictable and repeatable is the engineering task at hand.

Some ways they're approaching it:

- Reduce the requirement from 100% predictable to something lower yet acceptable.

- continuously add layers of checks and balances until we consistently hit an acceptable ratio of success:failure

- Wait and see if this is all eventually cost-efficient