The Quiet Protocol
Institutions run on protocols nobody wrote down. The visible rules are decoration; the protocol is the part that breaks when an outsider follows the rules literally.
Every institution has two layers. The first is the written rules: bylaws, org charts, codes of conduct, published procedures. These are the part anyone can read. The second is the unwritten protocol: which rules are enforced, in what order, with what tolerance, by whom, in response to what. The protocol is what the institution actually runs on.
The written rules and the protocol are not the same. They overlap, but the overlap is rough. Many rules are enforced inconsistently or not at all. Many protocol behaviours have no written backing. New members of the institution learn the rules in onboarding and the protocol by being corrected when they apply the rules in the wrong way at the wrong time.
This structure has a use: it lets the institution adapt. The written rules change slowly because writing them down requires consensus. The protocol changes at the speed of conversation between the people who actually run the place. An institution with only written rules would either ossify or reform constantly; the protocol is the shock absorber that lets the rules be slow.
The failure mode is that the protocol is invisible. Anyone trying to understand the institution from outside reads the rules, follows them, and finds that nothing they expected to happen does. They conclude that the institution is broken or hostile. Often it is neither; it is running its protocol, which the rules did not describe.
The operator's task is to make the protocol partially legible without writing it down — because writing it down would lock it in place, and the protocol's value is its mutability. This is a hard interface problem. Most institutions never solve it, and the asymmetry between insiders and outsiders that results is the institution's actual cost of doing business.