Boundaries are rules about YOUR behavior, not demands…

State relational boundaries as rules about your own behavior in response to others' actions ('I will leave the room if voices are raised') rather than as demands about others' behavior ('You are not allowed to yell'), preserving their sovereignty while protecting yours.

When This Fires

When setting any interpersonal boundary (Three components of an effective boundary)
When a boundary attempt feels like an argument about what the other person should or shouldn't do
When boundaries keep failing because the other person "won't cooperate" — reframe from demand to self-rule
When the boundary needs to work even without the other person's agreement

Common Failure Mode

Demand-framed boundaries: "You need to stop interrupting me." "You're not allowed to bring work into our vacations." "Don't raise your voice." These are demands disguised as boundaries. They depend on compliance and fail when compliance isn't offered. Sovereignty-framed equivalents: "I'll pause the conversation when interrupted and resume only when I can speak completely." "I'll schedule solo activities during vacation time that's used for work." "I'll leave conversations where voices are raised."

The Protocol

(1) For each boundary, write it first as a demand ("You should/shouldn't [behavior]") then convert to sovereignty ("I will [my action] when [their behavior occurs]"). (2) Verify: is the sovereignty version entirely within your control? Can you execute it regardless of their cooperation? If yes → it's a genuine boundary. If it requires their compliance → it's still a demand. (3) Communicate the sovereignty version: "When [trigger behavior occurs], I will [my response]." (4) The other person's choices remain their own — the boundary doesn't control them. It controls your response to their choices. (5) Follow through when the trigger occurs (Enforce boundaries consistently — inconsistent…). The boundary's power comes from consistent self-governance, not from the other person's agreement.