You're in over your head but you have the protocol. Good. The ritual. The correct procedure for handling something stronger than you. Here's what this probably means: you're interfacing with something that could destroy you if you handle it wrong. Production databases. Live deployment systems. Actual users depending on your code. Maybe a replicant who might be a combat model. The classical text says pleasant manners succeed even with irritable people. Your version: documentation and established procedures let you interact safely with systems that have the power to end you. The junior dev following code review protocol. The system admin running the deployment checklist for the hundredth time, still checking every box. The temptation is to get casual. You know this system, you've done it before, you can skip the boring parts. This is exactly when the tiger bites. Every catastrophic system failure has this moment: someone thought 'I know this well enough to skip the checklist.' That confidence—that presumption of mastery over the strong thing—is where conduct breaks down. Deckard administering the Voight-Kampff test never presumes control. He maintains the form. He stays in his role. He discriminates between high and low, tester and tested, human capability and replicant strength. The replicant doesn't snap his neck because he never gives it reason to. The protocol isn't bureaucracy. It's the accumulated wisdom of everyone who walked this path before you and didn't get bitten. When you're treading on the tail of the tiger, simple conduct—following the established pattern without arrogance—is what keeps you alive. Skip it and find out.