Maintenance is where a system tells the truth about itself. The polished diagram gives way to hand-written labels, shared passwords, half-remembered procedures, and the person everyone calls when something strange happens.
These are not necessarily signs of failure. They are evidence of adaptation: people keeping a system useful when reality exceeds its original specification.
This short note marks a trail to return to: how product teams might treat maintenance not as an afterthought, but as research material.