The Safety Workaround That Worked, Until It Didn't
Power it on, and it's supposed to be ready to go on its own, no operator steps. Then one day, after a couple of restarts, it just... wasn't. Here's the clever safety workaround that quietly caused it. I had to build one testing tool that could behave as two opposite safety systems, but only ever connected to one at a time, with both behaviours crammed into a single safety system, sharing the same connection ID, over FSoE. The textbook move would've been two separate, validated configs with only
