Skip to content

Archetype Overmatching Guardrail

Prevent familiar archetypes from being forced onto cases that only superficially resemble them.

The Diagnostic Story

Symptom: A familiar pattern is named early, and from that moment the inquiry closes. Evidence that fits gets collected; evidence that doesn't gets set aside. The team moves straight from recognition to intervention, confident in the match. Only later, when the prescribed fix fails, does anyone ask whether the pattern was right in the first place.

Pivot: Insert a deliberate checkpoint between recognizing a pattern and acting on it. Make the proposed archetype explicit, test whether its required structural features are actually present, compare it to near-neighbor patterns, and attach a confidence level that constrains how far action can proceed.

Resolution: Pattern use stays evidence-bounded: surface resemblance no longer counts as structural fit. Near-neighbor alternatives remain visible, counterexamples are preserved, and the confidence label keeps action proportionate to how well the case has actually been verified.

Reach for this when you hear…

[clinical diagnosis] “It looks like condition X, but let's actually run through the diagnostic criteria before we start treatment.”

[legal practice] “This case smells like the Martinez precedent, but I want someone to list where the facts actually diverge before we cite it.”

[product design] “Everyone keeps calling this a 'onboarding problem' — can we check what the retention curve actually shows before we rebuild the flow?”

Mechanisms / Implementations

  • Anti-Pattern Review
  • Case Comparison Matrix
  • Counterexample Search Session
  • Decision Confidence Label
  • Differential Pattern Review
  • Pattern Fit Checklist
  • Pattern Fit Scoring Rubric
  • Precedent Distinction Memo
  • Red-Team Pattern Match Review
  • Review Queue

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 7 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Design Pattern Overfit Guardrail · domain variant · recognized

Prevents familiar design patterns from being applied where contextual fit is weak.

Precedent Overmatch Guardrail · domain variant · recognized

Prevents a prior case or precedent from being treated as controlling when the structural conditions differ.

Differential Archetype Review · implementation variant · recognized

Compares several plausible archetypes before assigning a confidence-bounded match.

Confidence-Bounded Pattern Use · risk or failure variant · recognized

Allows partial or provisional use of a pattern while explicitly constraining actions to the confidence level of the match.