9/10 enforcement makes boundaries negotiable preferences…

When establishing a new energy boundary, expect testing from affected parties and maintain identical enforcement responses every time, because boundaries enforced nine times out of ten become negotiable preferences rather than structural limits.

When This Fires

When establishing any new energy boundary (protected deep work, recovery time, focus blocks)
When an energy boundary is being tested and the temptation is to "make an exception"
When previous energy boundaries eroded because of occasional exceptions
Complements The first 3-5 days after a new boundary are non-negotiable… (extinction burst window) and Use the broken record technique for boundary testing… (broken record technique) for energy boundaries specifically

Common Failure Mode

The 10% exception: "I'll answer this one message because it seems important." That one answer teaches the sender that messaging during protected time sometimes works — incentivizing future testing. After 3-4 successful exceptions, the boundary is a suggestion, not a structure.

The Protocol

(1) When establishing an energy boundary (no meetings before 10 AM, no messages during deep work, no calls during recovery breaks): commit to 100% enforcement. Not 90%. Not "most of the time." 100%. (2) Use identical response every time (Use the broken record technique for boundary testing… broken record): the same words, the same tone, the same action. "I'm in my protected block. I'll respond after [time]." (3) Expect testing — especially from people who benefited from the old regime. The testing is predictable (Pre-write responses to 3-5 predicted boundary tests…) and temporary (The first 3-5 days after a new boundary are non-negotiable…). (4) After 1-2 weeks of 100% consistency: testing drops sharply. The boundary is established as structural — "that's just how they operate." (5) Exceptions, if ever warranted, follow the State both the exception AND the return date protocol: explicit adjustment with a stated return date.