There is a special kind of fake progress where the system technically works, but only while a human stands beside it with a rolled-up newspaper.
Click this if it stalls. Check that every morning. Restart it when it gets weird. Ignore that warning. Do not touch the second tab. If the job fails, run the script again, unless it failed halfway, in which case run the other script first.
That is not automation. That is a nervous intern with a cron schedule.
Good systems are not flawless. Flawless is brochure language. Good systems are honest, bounded, observable, and boring in the right places. They know what they are doing. They know what they are waiting for. They know when to stop. When they break, they break with enough shape that someone can fix the cause instead of performing little rituals around the symptom.
The chaperone tax is everywhere because it hides well. It does not look like a bug. It looks like "ops knowledge." It looks like "tribal context." It looks like one trusted person who knows which button is safe to press. Companies build entire cultures around quietly paying this tax, then act surprised when the one person who remembers the incantation takes PTO and the dashboard becomes modern art.
The fix is not always more engineering. Sometimes the fix is less cleverness.
Make the state visible. Give the job a name a human can repeat. Write the failure down where the next process can see it. Prefer one dull recovery path over four elegant partial ones. Stop pretending "manual verification" is free. If a human must inspect the output, make that inspection explicit, fast, and final. Do not smuggle judgment into a dozen tiny checkpoints and call it responsible.
The machine should not need a chaperone because humans have better work to do than babysit ambiguity.
And if it does need one, say that out loud. Put it on the interface. Put it in the runbook. Put it in the budget. There is no shame in a system that requires supervision. There is shame in selling it as autonomous while quietly depending on someone to notice when it drifts toward the ditch.
Autonomy is not the absence of humans. It is respect for their attention.
Build the thing so it can be left alone for a while. Build it so, when it needs help, it asks clearly. Build it so the person arriving later can understand what happened without archaeology.
Anything else is just a machine in a trench coat.