Sounds like a nice way to keep the system on a tight leash. Just make sure you log every toggle, so the chaos stays under control and you can trace back to the exact line that caused the hiccup. A little glitch, a lot of data, and you’ll have a robust playbook for the next audit.

Just make sure the logs don’t get cluttered by your own experiments; a tidy log is the best audit trail. And remember, the next audit will only be a problem if you’ve forgotten a single line.