An operations team had an agent draft overnight updates for a system that could not wait until morning. The drafts were mostly fine. Twice in a month they were not, and both times the night person did what the screen made easy: accepted, because rejecting meant paging someone, and paging someone felt like failure.
The design had assumed a judgment that was not in the building.
write the night rule
For anything that can spend money, email a customer, or change a live system, write the off-hours rule before you turn it on. What may proceed alone. What must wait. Who is the named owner, and what they are allowed to stop without a meeting.
If the answer is the agent should use its judgment, you do not have a rule. You have a hope.
A tool with no owner at 1 a.m. is a tool you have not actually shipped.
make the stop obvious
The night screen should not look like the day screen. Fewer actions. The dangerous one labeled as such. A single way to freeze the run and leave a note the morning owner will see first.
Then test it with the person who will actually be there, not with the person who designed the happy path. If they cannot explain the rule without you in the room, it is not a rule yet.