Comment by former-aws

Agree with your pov, especially the idea that you can only reject hypotheses, not confirm them.

What I keep seeing operationally is that teams are forced to act before hypotheses can be tested or falsified. For example, inspections completed, assets redeployed, and customers responded to. Only later are they asked to prove correctness.

When that gap shows up for you, what was the concrete trigger? An audit, a customer dispute, a safety review, or something else?