Directory · B
Not sure this is the right entry? Run the check · New here? Start with the premise
Boundaries
3 min read · 607 words
A boundary isn't a wall, a punishment, or a demand. It's a decision about what you will do — not an instruction about what they have to stop doing.
Is this you?
Check whatever lands. Nothing is sent anywhere.
A boundary is the line where one operating system ends and another begins.
The Relationships entry established the concept: signals originating in another person’s hardware are not signals originating in yours. A boundary is the practical application of this distinction — the recognition that what another system produces, requires, demands, or broadcasts is information about that system, not a command to yours.
The machinery doesn’t naturally maintain this line. The social hardware was built to synchronize, to absorb, to treat another organism’s state as relevant data for its own threat-assessment. The wiring blurs the boundary by design. The alarm in one control room produces activation in the next one. The emotional state of a nearby organism becomes the emotional state of this organism. The system absorbs because absorbing was once survival-relevant — the group that synchronized its threat responses survived better than the group that didn’t.
Boundary maintenance is not a natural function of the hardware. It is a deliberate override.
WHAT BOUNDARIES ACTUALLY ARE
A boundary is not a wall. It is a filter. It allows information through — the other person’s state is received, acknowledged, registered — without allowing that information to commandeer the receiving system’s operation.
The difference between a wall and a filter: the walled system blocks all input. It does not receive, does not register, does not acknowledge. This is isolation wearing the language of protection. The filtered system receives fully — the other person’s state is seen, their signal is heard — and then makes a decision from the control room about what to do with the data. The data is processed. It is not obeyed.
Where boundaries are needed:
When another system’s emotional output consistently overrides this system’s own signal processing. When the one at the controls cannot identify their own state because another person’s state has filled the room. When requests from another system consistently override this system’s actual capacity. When the organism’s behavior is shaped more by what another person needs than by what the operator has assessed as appropriate.
Where boundaries are not the issue:
When the system is calling isolation a boundary. When the organism uses “I have boundaries” to avoid intimacy, vulnerability, or reasonable accommodation. When the filter has been set so tight that nothing gets through — this is not a boundary. It is the avoidance protocol from the Avoidance entry wearing better language.
THE PRACTICAL POSITION
To establish a boundary: identify what is mine and what is theirs. My emotional state or theirs? My responsibility or theirs? My capacity or their demand? The boundary is drawn at the line where the answer switches.
The machinery will produce guilt when a boundary is drawn. The social wiring reads the boundary as a potential threat to the bond — the other organism may disapprove, may withdraw, may classify this system as uncooperative. The guilt signal is the social monitoring system’s assessment that group standing may be at risk. The signal is real. The assessment may or may not be accurate. The one at the controls can receive the guilt signal while maintaining the boundary — which is, in itself, the practice of reading a signal without being run by it.
The boundary does not require the other person’s agreement. It is not a negotiation. It is a statement about where this system’s operation ends. The other system may or may not respect it. Their response to the boundary is their machinery’s output — and that, too, is information the filter receives without it becoming a command.
Why a boundary that needs their agreement isn't one
Most boundaries fail at the same place: they're written as instructions for the other person. I need you to stop commenting on what I eat. That's a request — a perfectly reasonable one — and like every request, it can be refused, forgotten, or agreed to and then ignored. Which is exactly what tends to happen, and then it reads as proof that boundaries don't work on this person.
A boundary is the other half of that sentence, and it's the half almost nobody writes down: and if it comes up, I'm going to change the subject or leave the room. That part needs nobody's cooperation. It's a description of your own behaviour, which is the only thing in the exchange you actually control. It holds whether or not they agree, whether or not they understand, and whether or not they think you're being unreasonable.
This also resolves the usual guilt, because it clarifies what you're doing. You aren't trying to control them. You're declining to keep absorbing something, and you're saying in advance what you'll do instead — which, done calmly and repeatedly, is about as far from punishment as it's possible to get.
One caution, because the word gets used as cover: a boundary is a filter, not a wall. It lets the other person's state through — you still see it, still care about it — and then you decide what to do with it from a position that's yours. Blocking everything out isn't a boundary; it's avoidance using better vocabulary, and it tends to cost you the relationships you wanted to protect.
What to actually say
Flat and short. A boundary delivered as an argument invites an argument; a boundary delivered as information mostly doesn't. No speech, no case, no listing of previous offences.
- The complete shape, both halves
I'm not going to keep talking about this. If it comes up again I'm going to change the subject.
- With a parent
I love you, and I'm not discussing my weight with you. If it comes up I'll go and do something else for a bit — it isn't a punishment.
- When it gets crossed again
I said what I'd do if this came up. I'm doing it now. That's all this is.
- When they say you've changed
I have. This is the version of me that can keep seeing you.
- Without any speech at all
That doesn't work for me.
- When they want to debate whether it's fair
You don't have to agree with it. I'm still going to do it.
Write the second half
Take one boundary that keeps failing. The failure is nearly always in the missing half.
Real questions
What's the difference between a boundary and an ultimatum?
Who it's aimed at. An ultimatum is a demand on their behaviour backed by a threat — stop doing this or else — and its purpose is to change them. A boundary describes your own behaviour and its purpose is to protect your capacity, so it works even if they never change at all. The practical tell is tone and need: an ultimatum needs them to comply and escalates when they don't. A boundary can be stated calmly, once, and then simply carried out.
How do I set a boundary with my mum or dad?
Smaller and less ceremonially than you're planning to. Family boundaries fail mostly because people save them up for one big conversation that doubles as a grievance review — which guarantees defensiveness and settles nothing. Pick one specific recurring thing, say one flat sentence about what you'll do, skip the history entirely, and then do the thing the next time it happens. Expect the first few to be uncomfortable, and expect accusations of coldness. Decades-old dynamics don't update on the first attempt.
Why do I feel so guilty setting boundaries?
Because the wiring that monitors your standing in a group reads it as a risk to the bond and fires a warning — which is exactly its job. The timing gives it away: the guilt usually arrives before any actual consequence, and often before you've even spoken. That makes it a prediction, not evidence that you did harm. You can feel it fully and hold the boundary anyway, and that specific combination is most of the skill. Waiting for the guilt to go away first means waiting forever.
What do I do when someone ignores my boundary?
You carry out the second half, immediately and without a speech. If there is no second half, you didn't set a boundary — you made a request, and it got declined. Repeating the request louder is the most common mistake here and it teaches the opposite of what you want: that the sentence is just a mood you pass through. The first time you actually do the thing you said you'd do is when the boundary becomes real, and it's worth far more than any number of conversations.
Am I setting a boundary or am I just avoiding them?
Useful question, and worth asking honestly, because the word is a comfortable place to hide. A boundary is a filter: you still receive them, still care how they are, still let the relationship exist — you've just stopped absorbing one specific thing. Avoidance blocks the whole channel. One test: can you name precisely what you're declining, in a sentence? If what you've actually got is a general wish not to deal with them, that's avoidance in better clothes, and it will cost you something you wanted to keep.
Do I have to announce a boundary, or can I just do it?
You can just do it, and for people who argue with every stated limit, quietly doing it often works better. Announcing has one real advantage — it gives someone who genuinely didn't realise a chance to adjust, and plenty of people take it. Announcing to someone who has ignored three previous announcements has no advantage at all. The announcement was never the mechanism; the behaviour is.