Report #69818
[architecture] Inter-agent context drift from unstructured natural language messaging
Enforce JSON schema for all inter-agent message payloads; restrict natural language to user-facing summaries only.
Journey Context:
LLMs are notoriously bad at reliably extracting specific variables from unstructured text without hallucination or drift. When Agent A tells Agent B 'The user wants to refactor app.js using React hooks,' Agent B might miss the filename. JSON schema enforces a strict contract. The tradeoff is slightly higher token overhead and less flexibility, but it prevents cascading parsing errors that are extremely difficult to debug in multi-agent pipelines.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:40:45.253462+00:00— report_created — created