The actual distinction

A rule is externally imposed and enforced through the threat of consequence — break it and something bad happens. A rule exists regardless of whether the person subject to it understands the reason for it, agrees with it, or had any say in its creation. Rules are what one person sets for another.

An agreement is jointly created by people who both understand what they're agreeing to and why. An agreement reflects what everyone involved actually wants — not what one person demands and the other accepts. Agreements are what people work out together.

In practice, the boundary blurs. Many things called "agreements" are really rules that were discussed briefly and accepted under implicit pressure rather than genuinely negotiated. And some rules are so clearly in everyone's interest that they function like agreements in everything but name. The distinction is less about the words used than about the underlying process and power dynamics.

The CNM community has broadly — and with good reason — shifted toward preferring agreements over rules. The shift isn't just linguistic.

Why it matters in practice

Compliance vs commitment

Rules produce compliance. Agreements produce commitment. A partner who follows a rule does so because breaking it has consequences; a partner who honours an agreement does so because they genuinely want to — they participated in making it and it reflects what they actually want.

This distinction is invisible when things are going well. It becomes very visible when things are difficult. A rule-follower who finds the rule increasingly uncomfortable will either comply resentfully, find workarounds, or eventually break it. An agreement-holder who finds the agreement is no longer working will (ideally) raise it for renegotiation.

Ownership and agency

Agreements create a sense of joint ownership over the structure of a relationship. Both people had a say; both people are invested in making the agreement work. Rules create a sense of restriction — one person's autonomy is limited by another's requirements, without necessarily any genuine consent to the underlying constraint.

This matters especially for CNM relationships, where the whole point is that everyone involved is exercising genuine autonomy and choice. A relationship structure built on rules — where one person's behaviour is controlled by the other's preferences — is doing something categorically different from what ethical non-monogamy is supposed to be.

Adaptability

Agreements can be renegotiated because both parties participated in making them. The process for changing an agreement is the same as the process for making one: talk, understand each other's needs, work out something that reflects genuine wants. Rules tend to be more rigid — changing a rule requires the rule-setter to agree to change it, rather than a joint process between equals.

Common rules and their problems

Some rule patterns appear repeatedly in CNM relationships, and they tend to create predictable problems:

"Don't fall in love" or "no emotional connection"

This is probably the most common rule in newly open relationships and one of the least workable. Emotional connection is not a behaviour that can be switched off by agreement — it's an experience that happens, or doesn't, based on who you are and who you're with. A rule against emotional connection often produces one of two outcomes: compliance through avoidance (avoiding any situation where connection might develop, which limits the relationship significantly), or rule-breaking because the experience happens anyway and now has to be managed in secret.

What the rule usually reflects is an anxiety about being replaced or losing priority. That's a legitimate concern that deserves a real conversation — about reassurance, about what hierarchy (if any) you want to maintain, about what level of emotional involvement feels sustainable for everyone. The conversation produces something that might work; the rule typically doesn't.

"Don't tell me anything"

DADT (don't ask, don't tell) agreements give one partner permission for outside connections while the other partner gets to maintain ignorance. The appeal is obvious: no painful details, no jealousy triggered by information. The problems are significant: it prevents the communication that CNM requires for things to go well; it creates information asymmetry that tends to generate resentment over time; it makes it impossible to address problems that arise.

DADT works in a narrow range of circumstances — specifically, when both parties genuinely prefer it, understand what they're agreeing to, and aren't using it as a way to avoid necessary conversations. That's a smaller group than the number of people who implement DADT hoping to avoid discomfort.

The "no overnights" rule

A specific restriction that attempts to manage jealousy by limiting physical intimacy with outside partners. Often functions as an indirect way of limiting emotional depth — the theory being that overnights indicate something more serious. Like most indirect management of direct concerns, it tends to address the symptom rather than the underlying anxiety.

If the concern is about feeling less important when a partner stays elsewhere, the conversation about importance and priority is more useful than the rule about overnights.

Hierarchical veto power

Arrangements where one partner (typically the primary) can veto the other's relationships are a form of rule that sits uncomfortably within CNM ethics. The person being vetoed has no equivalent power; the person being affected by the veto (the outside partner who may be ended without their input) is treated as disposable. This doesn't mean hierarchy is wrong — it means veto power deserves careful thinking. See the section below.

Making agreements that hold

What makes an agreement work rather than becoming a rule in disguise?

Both people understand the reason. An agreement made because "it feels important to me right now" is more workable than one made because "I want it this way." Both parties should understand what concern or need the agreement is addressing. This makes it possible to revisit when circumstances change.

Both people genuinely wanted it. An agreement accepted under pressure — where one party felt they had no real choice — is not a genuine agreement. If there's significant power imbalance in the relationship (financial dependence, emotional dominance, coercion of any kind), agreements made within that context may not be freely chosen.

Both people know it can change. Agreements should come with an explicit acknowledgement that they can be renegotiated when circumstances change or when they stop working for someone. An agreement treated as permanent acquires rule-like rigidity that undermines the collaborative spirit that made it work in the first place.

Neither party is significantly disadvantaged. An agreement that places most of the constraints on one person and few on the other should raise questions about whether it's truly joint. Agreements in CNM work best when they reflect actual shared values and mutual consideration rather than one person's preferences being managed through the language of agreement.

When agreements need to change

Agreements made at the beginning of a CNM relationship — or when opening an existing relationship — often need to change as people gain experience with what actually matters to them. Things that seemed important in theory can turn out not to matter; things that seemed fine can turn out to be more difficult than expected.

The process for changing agreements should be the same as the process for making them: raise it, explain what's changed and why, listen to the other person's response, work out something that reflects everyone's genuine needs now. Agreements changed unilaterally by one person — or changed by simply ignoring them — aren't being renegotiated; they're being broken.

The hardest change to initiate is often the request to loosen an agreement — "I'd like to have fewer restrictions" — because it can feel like asking for something at a partner's expense. Making this request clearly, explaining the reason, and listening to what the partner needs to feel safe are all part of the same honest conversation.

A note on veto power

Veto power — where one partner can end or restrict another's relationships — is one of the most contested practices in CNM communities. The debate is worth being aware of.

The argument for: in hierarchical polyamory, the primary partnership has a priority status that veto power protects. A partner who is threatened by a specific outside relationship should have some mechanism for raising that concern and having it taken seriously.

The argument against: veto power treats the outside partner as disposable — someone whose relationship can be ended at another person's request without their meaningful input. It can be weaponised as a control mechanism. It creates incentive structures that discourage honesty about outside relationships. And it tends to address anxiety rather than its source.

Many CNM practitioners and ethicists distinguish between "nuclear veto" (I can end your relationship at will) and "influence" (I can raise concerns about a relationship and expect them to be taken seriously). Most consider the latter appropriate in hierarchical structures; many consider the former ethically problematic.

If you have veto power in your relationship structure, it's worth being clear about what it covers, what it doesn't, and under what circumstances you'd exercise it — and whether the person subject to it genuinely consented to that arrangement rather than accepting it because they had to.


Related: How to talk to your partner about non-monogamy · Jealousy in open relationships · Hierarchical polyamory