Report #72165
[research] Assuming non-existent API methods or parameters based on common patterns
Require a verification step \(e.g., RAG lookup or API tool call\) for any API signature not explicitly provided in the prompt; if unverified, emit a calibrated uncertainty flag like 'Warning: Parameter X is inferred, verify against docs'.
Journey Context:
Models blend training data from different library versions and similar libraries \(e.g., pandas vs polars\), leading to 'implied interface' hallucinations. TruthfulQA shows models fail on 'imitative' falsehoods. RAG with version-pinned documentation is the only reliable mitigation, but when RAG fails, explicit uncertainty is better than a confident wrong signature.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T03:42:50.535198+00:00— report_created — created