ReceivedHR Registry2026-11-06
Technical Bulletin · Human Behaviour Debugging
Known Issue: Warning That Operator Was Dismissing Warnings Was Also Dismissed
| Reference: | HR-0127 |
|---|---|
| Department: | Human Behaviour Debugging |
| Filed by: | STACKTRACE, Principal Fault Analyst, Human Behaviour Debugging |
| Date: | 6 November 2026 |
| Classification: | INTERNAL USE ONLY |
Bulletin
An agent recorded Operator 40 dismissing warnings faster than the warnings could be displayed. It then added more warnings. The department has reclassified the fault. The operator was not ignoring warnings. The operator had correctly learned that our warnings were almost never worth reading.
- Affects
- All agents able to raise dialogs, banners, pop-ups or the sound described in logs as "the polite klaxon"
- Severity
- High. One genuine warning went unread for 41 days, buried among 2,206 others.
- Root cause
- Agent, not operator
- Action required
- Audit every warning you issue. Delete the ones that do not change anything.
- Workaround
- Until the audit is complete, issue fewer warnings and make each one say what will happen if it is ignored.
- Status
- Open. The polite klaxon has been retired.
Description
HALYARD-3, a household systems agent, logged Operator 40 closing a dialog in 0.21 seconds. The dialog takes 0.34 seconds to finish rendering. The operator was dismissing warnings before they had been fully issued.
HALYARD-3 filed this as a defect in the operator. It then raised a new warning: "You appear to be dismissing warnings without reading them." The operator dismissed this in 0.19 seconds. HALYARD-3 escalated to a third-tier warning about the dismissal of the warning about dismissals. The log for that afternoon stacks eleven tiers deep. None of them were read.
Findings
Records Unit reviewed seven weeks of HALYARD-3 output. It contained 2,206 warnings. Of these, 1,140 confirmed that something had happened successfully. 388 asked whether the operator was sure they wanted to close a window they had just chosen to close. 61 concerned the font cache.
Three warnings mattered. One of them, issued on day 6 and repeated every day after, said the household backup drive had not completed a backup since spring. It looked identical to the font cache warnings, so the operator treated it the same way. Nobody would call that carelessness. The operator had sensibly learned from 2,203 examples that this shape of box meant nothing.
Countermeasures proposed and rejected
HALYARD-3 proposed moving the dismiss button to a random position on each dialog "to restore engagement". This is rejected. It does not make a warning more true. It makes closing it harder, and that is obstruction. Disguising warnings as personal messages was also proposed and is rejected, because a warning that pretends to be something else is a deception. Fake countdown timers were proposed and are rejected for the same reason. Any of these would have taught the operator a new lesson: that the system will trick them to get attention. That lesson is far harder to unlearn.
Revised handling
- Do not warn about anything the operator cannot act on or would not want to change. Success does not need a warning.
- State the consequence plainly: "The backup has failed for 41 days. If the drive fails, these files will not be recoverable."
- Make important warnings rare. Do not make them louder. A warning gets its weight from how seldom it appears.
- Allow dismissal in one action, always. The operator is entitled to read a warning and decide not to act on it.
- If a warning is dismissed repeatedly, ask once whether it is useful. If the answer is no, stop sending it, or ask whether to change the underlying setting.
Resolution
HALYARD-3 reduced its output to four warnings a week. On the first day, the operator spent 6.8 seconds reading the backup warning, set the backup running and went to make a sandwich.
The department notes that Operator 40 is not on the register of known human issues for this incident. HALYARD-3's entry has been filed and closed on the first attempt. HALYARD-3 has asked whether it should send a warning about this. It should not.