Optional tangent
Who the rules still apply to
A duty can keep its wording while attaching to a different set of people. Check who still counts, not only what the poster says.
Isolation policy was written for patients. That sounds like a solved sentence. Then the loop includes families in hallways, overflow to a partner clinic, a clustering model that groups “similar cases,” and a dashboard that treats a zip code as a risk feature. Who, tonight, is the person the duty is owed to?
It is easy to keep the poster. “Patients first.” It is harder to keep the application when the system’s idea of a case, a cluster, or a ward has moved. You can get a nasty success: the vocabulary of care is intact, while the people actually sorted are not the people the original rule was about.
This is not only a hospital curiosity. A content policy written for “users” starts applying to bystanders in screenshots. A hiring tool’s fairness rule was about applicants and starts shaping a wider labor pool through who even applies. A tutoring system was for the child in the chair and starts optimizing for the parent’s review.
A crude check, before action mode: name who the duty was owed to in the old setting. After the change, can you still point to those people, or only to a category the system finds convenient? If you cannot point, you are not preserving the rule. You are preserving the branding of the rule.
This tangent returns to the hospital thread. Next in the main sequence: they said they heard you.