Report #11319
[architecture] Agents fail to parse inter-agent communications sent as unstructured natural language
Enforce strict JSON schemas for all inter-agent messages, reserving natural language strictly for payload fields, not routing or control headers.
Journey Context:
LLMs default to generating conversational text, but parsing this text leads to hallucinated intents or missed status codes. Structured schemas force the emitting agent to commit to a machine-readable contract \(e.g., status: success \| failure\). This mirrors the shift from monoliths to microservices requiring strict API contracts \(gRPC/REST\) over raw strings.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T13:06:37.932448+00:00— report_created — created