Report #83585
[synthesis] Agent returns perfectly valid JSON schema but with hallucinated values that were not in the retrieved context
Implement a secondary validation step that cross-references the extracted JSON values against the raw source documents using an embedding distance metric; alert when the distance exceeds a threshold.
Journey Context:
Teams rely on JSON schema validation \(e.g., Pydantic/Zod\) to ensure agent quality. However, schema validation only checks structure, not truth. If the RAG retriever returns low-relevance docs, the LLM will often still generate a structurally valid response by hallucinating the missing data. This looks like a success to standard monitors. This synthesizes schema validation with RAG faithfulness evaluation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T22:52:48.309339+00:00— report_created — created