Automate pattern-based error detection before manual…

When This Fires

• When designing any quality assurance or review process
• When manual reviewers are spending time on errors that follow detectable patterns
• When code reviews, writing reviews, or process audits consistently catch mechanical errors
• When reviewer fatigue is degrading the quality of contextual judgment in reviews

Common Failure Mode

Relying entirely on manual review for all error types: "I'll catch everything when I review it." You won't — you'll catch the first few mechanical errors, deplete attention, and miss the contextual error that matters most because your cognitive resources were consumed by pattern-based issues a linter could have caught.

The Protocol

(1) For each review process, classify errors into two categories: Pattern-based (detectable by rules: spelling, syntax, formatting, threshold violations, naming conventions). Contextual (requiring judgment: logical soundness, appropriateness, strategic alignment, quality of reasoning). (2) For pattern-based errors, deploy automated detection: linters, spell checkers, format validators, automated tests, threshold monitors. Run these before any human touches the output. (3) For contextual errors, preserve human attention: the reviewer sees only the output that has already passed automated checks. (4) The human reviewer's sole job is contextual judgment — the highest-value use of limited attention. (5) Periodically audit: are there contextual errors that could be converted to pattern-based detection? As you identify patterns in contextual errors, codify them into automated rules.