Report #22366
[architecture] Downstream agent fails to parse unstructured output from upstream agent
Enforce strict JSON schema contracts at the boundary between agents using structured outputs or function calling, treating the output as an API contract rather than conversational text.
Journey Context:
LLMs default to chatty text. Passing this directly forces the next agent to parse natural language, causing fragility. Alternatives like regex extraction fail on edge cases. Enforcing a JSON schema forces the upstream agent to serialize its state, making the boundary deterministic and testable, though it slightly constrains the upstream agent's expressiveness.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T15:57:04.271380+00:00— report_created — created