When a conversation is not permitted

Some organizations have to keep two of their own parts apart. A firm whose research desk may not talk to its traders; an agency whose investigators may not talk to the team being investigated; a council whose procurement evaluators may not talk to the bidders. The rule has several names — information barrier, ethics wall, need-to-know separation — and Yeetline enforces it as an authorization rule, the same kind as "are you a member of this room".

What you will see

One of three things, depending on how your deployment has set the wall up.

Refused. A sentence saying that the conversation is not permitted by this deployment's policy, and who to ask about it. Nothing is delivered.

Held. A sentence saying the conversation needs approval, that a request has been recorded, and who to ask if it is urgent. Somebody with the authority to decide is told; when they decide, you are told the answer.

Allowed, with a notice. The conversation works, and you are told once that a policy boundary runs through it. That is the point of the mode: a boundary nobody is told about is a boundary nobody can respect.

Why you are not told more

You will notice that the refusal does not say which wall stopped you, or which team the other person is in, or what the rule's reason is. That is not the server being unhelpful. In a regulated organization, the fact that a wall exists — and where it runs — is itself information. A message saying "you may not talk to Trading" would tell you that there is a Trading desk, that you are on the wrong side of a wall from it, and which of your colleagues is on the other side of it.

So the refusal is one constant sentence and the name of somebody to ask, and everything else about it goes to the people whose job it is to review the policy. This is the same reason a non-member of a private conversation is told "no such conversation" rather than "you are not a member of that": the wording of a refusal is part of what is being withheld.

What it cannot do

It cannot unsay anything that was already sent. It cannot stop two people who are sitting in the same room from talking. And it is not encryption: a barrier decides who may be in a conversation, in exactly the same place membership is already decided. What keeps the contents unreadable is the same end-to-end encryption that always did.

Last changed 2026-10-06