Report #35150
[architecture] Downstream agent fails because upstream agent output changed JSON structure
Enforce strict JSON Schema contracts at the agent boundary using programmatic validation \(e.g., Pydantic/Zod\) before semantic processing, rejecting or retrying invalid outputs.
Journey Context:
LLMs are stochastic; relying on prompt engineering alone \('output valid JSON'\) fails at scale because minor format deviations break downstream parsers. Programmatic validation at the handoff point prevents cascading parsing errors. The tradeoff is added latency for validation and potential retry loops, but it guarantees structural integrity across agent boundaries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:27:54.988019+00:00— report_created — created