Note that we have decades of experience and skill at easily teaching basic stick and rudder flying skills, however deploying independent systems/automation analysts under emergency conditions is highly problematic and will likely result in more tragedies.

I'm just saying its simpler, cheaper, and safer to deploy people who can troubleshoot simple flying systems rather than to deploy people who will have to debug untested and complicated automation systems on the fly. It would be the most extreme field service posting, ever.

What we have here is an over optimization problem; we "have to" build unflyable aircraft to keep up with everyone elses level of recklessness to squeeze a couple more hyper-financialized pennies out of the system or be replaced by someone reckless enough to do it. Traditionally regulation helps in these situations. The aircraft of the future is far more likely to have networking and interconnected processors prohibited by law for safety reasons than to be an internet of things self-flying appliance. That would result in a nice simple, admittedly lower performance, far more reliable overall system. Non-networked non-interconnected control microprocessors seem safe enough so far, but making an infinitely complicated hyper optimized system seems in practice to result in planes falling out of the sky too often.