Report #96948
[architecture] Unstructured text passing between agents causes silent semantic drift and parsing failures that compound through the chain
Enforce JSON Schema contracts at every agent boundary using Pydantic models or OpenAI Function Calling schemas; reject outputs that fail strict validation \(including type coercion and required field presence\) rather than attempting fuzzy parsing or 'helpful' repair.
Journey Context:
Teams often start with 'pass the LLM output to the next agent' as plain text, assuming the context window handles continuity. In practice, this leads to telephone-game degradation where Agent 2 misinterprets Agent 1's ambiguous summary or hallucinates fields. Structured schemas act as compiler-type checks for agent interfaces, failing fast on contract violations rather than propagating errors. The resistance comes from the friction of strict typing in a probabilistic system, but without it, debugging multi-agent failures becomes impossible.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T21:18:43.059059+00:00— report_created — created