High confidence is a trigger for more scrutiny, not less…

When This Fires

• When you feel very confident about a bug's root cause before thorough investigation
• When a technical architecture decision feels "obvious" and doesn't seem to need review
• When you're about to skip verification because you're "sure" about the answer
• Any technical conclusion where confidence arrives before comprehensive evidence

Common Failure Mode

Using high confidence to justify skipping steps: "I'm pretty sure this is right, so I'll skip the load test." The higher your confidence, the more dangerous the skip — because the neural gating effect means you're least likely to notice the evidence that would change your mind.

The Protocol

When confidence in a technical conclusion exceeds 8/10: (1) Notice the confidence level — rate it explicitly. (2) Treat it as a trigger: "My confidence is high, which means my evidence-filter is narrowing. I should search harder, not less." (3) Deliberately seek disconfirming evidence: "What would make this wrong?" (4) Maintain or increase verification effort — the opposite of what confidence suggests. (5) If the conclusion survives active falsification attempts, your high confidence is earned. If it doesn't, you've caught an error that high confidence would have hidden.