[Control Snapback] does not always announce itself. Most of the time it does not look like a retrieval at all. It looks like helpfulness, or standards enforcement, or just the operator being thorough. That is what makes it difficult to catch and easy to repeat.

The four override patterns are the behavioral expressions of [Control Snapback] — the four distinct ways an operator retrieves authority from a hire without naming it as a retrieval.

The Public Override. The operator reverses the hire's call in front of the cast, the Guest, or both. The hire made a decision inside their domain. The operator did not agree with it and said so — out loud, in the room, with witnesses. The call is corrected. The hire's authority is not just retrieved in that moment; it is publicly reduced. Every cast member who saw it now knows the hire's calls are subject to revision. The hire knows it too. They stop making calls that might get revised.

The Silent Redo. The operator re-performs the hire's work without saying anything. The prep was done. The operator walked through, saw it differently, and redid it. No conversation. No named standard that was missed. Just the work, done again, the operator's way. The hire finds it later — or does not find it at all. Either way the message landed: their version was not acceptable. The standard that makes it unacceptable lives only in the operator's head.

The Walk-Through Adjustment. The operator makes small, constant corrections throughout the shift. Not one override — a hundred micro-ones. The section is reset. The station is reorganized. The table is touched up. The order is slightly modified. Each one is individually defensible. Collectively they communicate one thing: the hire is executing inside a domain the operator has never actually left. The hire eventually stops making decisions and waits to be corrected instead.

The Retroactive Standard. The operator names a rule only after it has been missed. The hire did not know the standard existed — because it did not exist in writing, in training, or in any documented form. It existed in the operator's expectations, which is not the same thing. The hire is held accountable to a standard they could not have met because they could not have known it. The corrective is experienced as arbitrary. The hire's response is to stop exercising judgment and start asking permission instead.

All four produce the same outcome: the hire stops owning the domain. Not because they were told to hand it back — because the environment made it clear that ownership was not real. [Role Drift] is the accumulated result of these patterns running unchecked. The hire did not drift — the operator pushed them there, one override at a time, without ever knowing they were doing it.

The diagnostic the operator runs before [The Ten-Minute Close]: which of these four ran this week? If the answer is any of them — the question is not whether the hire failed the standard. The question is whether the standard was documented, known, and fair before the moment it was applied.