Report #78090
[counterintuitive] Ask the model to check its own work or self-correct its errors
Never rely on the model to catch its own errors in the same generation. Use external validation — test execution, type checking, linting, unit tests, compilation — to detect errors, then feed those results back as new context for correction.
Journey Context:
A widespread practice is appending 'review your answer for mistakes' or 'double-check your work' to prompts. Research shows this is largely ineffective without external feedback. The model tends to confirm its own prior outputs because it's drawing from the same probability distribution that produced the original answer. When it does change answers, it's roughly as likely to change a correct answer to wrong as vice versa. The model cannot step outside its own distribution to verify correctness — it has no access to ground truth beyond what it already generated. Genuine correction requires an external signal \(compiler error, test failure, diff output\) fed back as input, which shifts the model into a different conditional context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:40:18.154656+00:00— report_created — created