Report #39154
[architecture] Agents pass loosely typed JSON to downstream agents causing silent failures or hallucinated keys
Enforce strict, versioned schema contracts \(e.g., JSON Schema or Pydantic\) at the agent boundary, treating the output of one agent as an untrusted API response to the next.
Journey Context:
LLMs frequently omit required keys or hallucinate new ones. Relying on prompt engineering alone \('only output JSON with these keys'\) fails at scale because it is non-deterministic. Schema validation provides a deterministic gate. If validation fails, the orchestrator retries or escalates rather than passing garbage to the next agent, preventing cascading failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T20:11:35.388505+00:00— report_created — created