Report #63880
[counterintuitive] Instructing the model 'Do NOT hallucinate' or 'Do not write buggy code'
State positive requirements explicitly and implement verification loops \(e.g., 'Verify all imports exist' or use tool-use to run a linter\).
Journey Context:
Negative prompting often backfires because it primes the model on the exact failure mode \(the 'pink elephant' problem\). Telling a model 'don't hallucinate' gives it no actionable heuristic; it just increases the attention weight on the concept of hallucination. Modern models respond far better to positive constraints \('Base your answer strictly on the provided context'\) and self-correction mechanisms where the model uses tools to verify its own output against a linter or test suite.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:42:35.819851+00:00— report_created — created