Report #46600
[architecture] Unstructured text passing between agents causes cascading parsing failures
Enforce strict JSON Schema contracts at agent boundaries using structured output features \(e.g., OpenAI function calling/JSON mode\) and validate payloads before routing to the next agent.
Journey Context:
Developers often let agents chat in natural language, assuming the next agent will 'figure it out.' This breaks under scale because LLMs hallucinate formatting or omit required fields. Alternatives like regex extraction are brittle. JSON Schema provides a deterministic contract: if validation fails, the orchestrator can trigger a targeted retry with the exact validation error, rather than letting the error propagate. Tradeoff: strict schemas reduce the flexibility of natural language but guarantee machine-readable handoffs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:41:36.487038+00:00— report_created — created