We often treat “automation” and “documentation” as enemies. The prevailing DevOps wisdom is that if you have a runbook, you should automate it into a script. If you can’t automate it, you tolerate it as toil.
However, in complex cloud operations (CloudOps), there are persistent “Non-Automated Domain” tasks that require human judgment, complex troubleshooting, or legacy system interaction. When these tasks fail, it’s rarely because the engineer lacked skill; it’s because the documentation was ambiguous, outdated, or written by someone who left the company three years ago.