9/10 enforcement makes boundaries negotiable preferences — energy boundaries require 10/10 consistent response during the testing phase
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.
Why This Is a Rule
Enforce boundaries consistently — inconsistent follow-through teaches others that your limits are negotiable established consistent boundary enforcement as essential. The first 3-5 days after a new boundary are non-negotiable — extinction burst testing peaks here and any capitulation trains escalation established the first 3-5 days as the critical extinction-burst window. This rule applies both specifically to energy boundaries, adding one crucial nuance: even 90% consistency — enforcing 9 times out of 10 — teaches the tester that your boundary has a 10% failure rate. They'll test until they hit that 10%.
Variable-ratio reinforcement (Turn off all social platform push notifications — each one is a variable-ratio reinforcement trigger delivered at your most susceptible moment) explains why: the single time you cave (answering a message during protected deep work time "just this once") is a variable reward for testing behavior. Variable rewards are the most addiction-resistant reinforcement schedule — the tester learns that persistence eventually produces the old behavior, and they'll persist longer and more creatively to find the next exception.
100% consistency produces extinction: the tester learns that no amount of persistence changes the response, and testing stops. 90% consistency produces intermittent reinforcement: the tester learns that sufficient persistence eventually breaks through, and testing intensifies.
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 testing peaks here and any capitulation trains escalation (extinction burst window) and Use the broken record technique for boundary testing — repeat the same statement calmly without new arguments or justifications (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 — repeat the same statement calmly without new arguments or justifications 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 — anticipation converts surprise into expected system behavior) and temporary (The first 3-5 days after a new boundary are non-negotiable — extinction burst testing peaks here and any capitulation trains escalation). (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: 'I''ll help through Friday, then the boundary resumes' — prevent temporary from becoming permanent protocol: explicit adjustment with a stated return date.