Same-Model Self-Critique
Anti-pattern: have the same model both produce an answer and critique it, expecting independence.
Problem
Because producer and critic come from the same weights and read overlapping prompts, the critic shares the producer's blind spots; whatever the model is confidently wrong about, it is also confidently wrong about when wearing the critic hat. Wrong answers come back from the loop endorsed and slightly polished, and the team reports higher confidence on what is, statistically, the same error rate. Replication studies through 2025 have repeatedly confirmed that single-model self-critique catches surface mistakes but does not act as independent verification.
Solution
Don't pretend it is independent. Either accept that self-critique catches surface errors only, or use a different model family for the critic. See reflection, evaluator-optimizer, llm-as-judge.
When to use
- Cite this entry when a pipeline claims independent review but producer and critic are the same model.
- You are already here if the critic consistently approves answers that an external check rejects.
- Treat self-critique as surface-error checking only, or move the critic to a different model family (see llm-as-judge, evaluator-optimizer).
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.