You were taught to set boundaries nicely. The soft preamble. The three reasons. The apology bolted onto the front, before you have even said the thing. I hope this is okay, but. You did everything the etiquette asked of you. And the boundary was crossed again by Thursday.
Here is why. You built a request and called it a boundary.
Etiquette is the art of not making other people uncomfortable. A boundary, by definition, makes someone uncomfortable. That is not a flaw in the boundary. That is the mechanism. So the moment you route a boundary through etiquette, you hand it a first priority, their comfort, that is in open conflict with its actual job, your limit. You have designed the thing to fail, and then you are surprised when it does.
Etiquette and engineering optimize for completely different outcomes. Etiquette optimizes for how the thing lands. Engineering optimizes for whether it holds. Etiquette is a performance staged for the other person. Engineering is a structure that stands whether or not they applaud it. Etiquette needs their agreement. Engineering needs only your follow‑through.
And that difference only shows up under load. A boundary you can hold only when the other person is being reasonable is not a boundary. It is a preference that survives in good weather. Real structures are rated for load. They are built to hold at the exact moment force is applied, when the person pushes, sulks, guilts, or escalates. That pressure is not the boundary failing. That pressure is the test the boundary was built for.
This is also why the over‑explaining backfires. Every reason you add is another handle for them to grab and negotiate. Etiquette says explain yourself thoroughly, be considerate, make your case. Engineering says a specification does not argue for itself; it states a tolerance and stops. "No" is a complete sentence, not because it is rude, but because it is structurally sound.
A boundary that depends on their permission was never yours to begin with.
Because the boundary was never really the sentence. The sentence is just the announcement. The boundary is the action you take when the line is crossed anyway, an action that has to be entirely within your control, or it is not engineering, it is a wish. An engineer does not hope the beam holds. They rate it, build to the rating, and it holds under load whether or not anyone in the room says thank you.
So stop trying to set a boundary politely. Politeness was never the assignment. You can deliver a boundary with real warmth, and warmth is welcome, but warmth is finish work on a structure, not a substitute for one. You are not being difficult. You are being load‑bearing.
Etiquette asks whether they are comfortable. Engineering asks whether it holds. Build the one that holds.