Report #42704
[architecture] Unverified agent outputs propagate hallucinations downstream
Insert deterministic, non-LLM validators \(JSON Schema \+ Pydantic \+ business rule assertions\) between every agent transition; reject and retry up to N times before circuit-breaking.
Journey Context:
The anti-pattern is assuming Agent B will 'handle' bad input from Agent A. In practice, LLMs amplify errors— Agent B may confabulate details to fit the malformed input, creating a compound error that's untraceable. Some suggest using another LLM to 'check' the output, but this introduces recursive trust issues and cost blowouts. The robust pattern is consumer-driven contracts: Agent B publishes its input schema, and a lightweight validator \(non-LLM\) enforces it. If validation fails, the message is dead-lettered for human review. This trades a small latency cost \(milliseconds for Pydantic vs seconds for LLM\) for reliability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T02:08:47.659903+00:00— report_created — created