Report #88904
[architecture] Unstructured prompt-based contracts between agents lead to hallucinated keys and broken handoffs
Enforce strict JSON Schema validation at the orchestration layer for all inter-agent messages, using structured output generation \(e.g., function calling\) rather than relying on prompt instructions.
Journey Context:
Developers often ask Agent A to 'respond in JSON with keys X, Y' and pass it to Agent B. Under complexity, A drops keys or hallucinates new ones, causing B to crash or hallucinate further. Treating the agent boundary like a network API with a strict schema acts as a compiler, failing fast at the boundary rather than propagating garbage state downstream.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:48:57.844453+00:00— report_created — created