Field Notes on Iron Unplug Verification
Return trips to verify appliance status have become a standard appendix to the act of leaving the house.
07:43
Subject ironed garments. Subject unplugged iron. Subject left room.
07:44
Subject returned to room to verify iron was unplugged.
Iron was unplugged.
07:52
Subject reached building exit. Subject paused. Subject returned to apartment to verify iron was unplugged.
Iron was unplugged. Same iron. Same status.
Observational Notes
People check whether an iron is unplugged after leaving the room because memory of unplugging feels less reliable than the risk. This discrepancy is the entire engine of the behavior. The iron is not malfunctioning. The memory is not defective. The risk is, by most calculations, small. None of these facts reduce the frequency of verification.
Iron unplug verification solves the immediate inconvenience once. That success makes repetition feel safer than reconsidering the behavior from scratch.
On the Nature of Controls
The machine has clear controls. A switch indicates power state. The switch was used. The switch is visible and legible. The machine does not hide its status.
This is insufficient. Ownership of those controls is socially distributed rather than technically defined. The question is not whether the iron is off. The question is whether the person who left the room can certify it.
Certification requires presence. Presence requires return.
Status at End of Study Period
After enough repeats, the workaround survives even when the original inconvenience is gone. Subjects who have verified the iron many dozens of times report no reduction in the felt need to verify. The behavior does not extinguish through repetition. It appears to sustain itself through repetition.
Under the governing rule, one successful use of iron unplug verification creates precedent for the next similar moment.
Notes for Future Field Visits
The verification ritual extends, in documented cases, to the gas stove, the front door, and the water heater. Each appliance has developed its own return-trip protocol. These protocols operate independently and may conflict in scheduling.
This is beyond the scope of the present notes.