Report #96698
[architecture] Cascading parse failures when Agent B receives unexpected JSON structure from Agent A
Enforce strict structural contracts \(e.g., JSON Schema, Pydantic\) at the agent boundary using structured outputs, and reject non-conforming payloads before executing Agent B's logic.
Journey Context:
Prompting Agent A to 'return JSON' is fragile; LLMs frequently omit keys or change types. If Agent B expects result.data but gets result.output, it crashes or hallucinates. Strict validation at the boundary allows Agent A to self-correct \(via retry\) or triggers a deterministic fallback before Agent B even runs, preventing cascading multi-agent failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:53:39.068607+00:00— report_created — created