Report #84483
[architecture] Cascading parsing failures when passing unstructured JSON between agents
Enforce strict JSON Schema contracts at the boundary of every agent handoff, validating the payload before execution of the next agent begins.
Journey Context:
LLMs frequently omit keys or hallucinate types when generating JSON. Relying on prompt-only constraints \('output valid JSON'\) fails at scale in multi-agent systems. Schema validation acts as a hard compiler-like boundary. If validation fails, trigger a self-correction loop on the generating agent rather than passing malformed garbage downstream, which causes opaque KeyErrors in subsequent agents.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T00:23:45.905608+00:00— report_created — created