Report #72349
[counterintuitive] Using negative constraints like 'Do not hallucinate' or 'Do not make up APIs' to prevent fabrications
Provide strictly bounded context \(e.g., retrieved documentation\) and instruct the agent to only use provided tools/APIs, explicitly defining the fallback action if information is missing \(e.g., 'If the API is not in context, use the search tool'\).
Journey Context:
Telling an LLM 'don't do X' is ineffective because language models predict the next token based on the context; mentioning 'hallucination' or 'fabrication' actually primes the model's attention towards those concepts. Furthermore, models lack a reliable internal threshold for 'knowing' versus 'guessing.' The fix is not a negative constraint, but a positive structural constraint: bounding the allowed solution space to a RAG context and providing a deterministic fallback action when context is insufficient.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T04:01:35.626718+00:00— report_created — created