First violation
After the first boundary violation by the same person, conduct repair with clearly stated consequences; after the second violation, enact the stated consequences rather than issuing new warnings, to distinguish boundary flexibility from boundary erosion.
When This Fires
- After the first boundary violation by a specific person has been repaired (Repair boundary violations within 24 hours) with consequences stated
- When the same person violates the same boundary a second time
- When you're tempted to issue "one more warning" — the warning was the first violation's repair
- Complements Graduate your refusals (graduated no) and Escalate from behavior description to pattern-naming… (pattern-naming) with the consequence enactment rule
Common Failure Mode
The infinite warning loop: "I've told you five times about this..." Five warnings means five opportunities to learn that warnings have no consequences. The other person has been trained by five data points that violations produce words, not actions. By warning six, neither party takes the boundary seriously.
The Protocol
(1) First violation: repair (Repair boundary violations within 24 hours) with explicitly stated consequence: "This crossed the boundary. If it happens again, I will [specific consequence]." (2) Second violation: enact the stated consequence. Not a new warning. Not "I'm serious this time." The consequence you stated after the first violation is now executed. (3) The consequence should be proportional and natural (Use natural consequences, not punitive ones — 'if scope…): not punishment but the natural result of the violation. "I stated that if meetings continue to overrun, I would start leaving at the scheduled end time. That's what I'll be doing." (4) After consequence enactment, reassess: does the person adjust their behavior? If yes → the enforcement worked; the boundary is now established. If not → this is a relationship-level incompatibility that consequences alone can't resolve.