Report #4634
[architecture] Agents exchange free-form natural language and silently misparse each other's intent, output format, or task status.
Define typed message schemas for every inter-agent exchange \(Pydantic models, JSON Schema, or protobuf\). Use a protocol such as A2A that standardizes Task, Message, Part, Artifact, and error payloads.
Journey Context:
Natural language feels flexible but is a lousy machine-to-machine protocol: one agent's 'done' is another's 'done for now'. A2A deliberately uses JSON-RPC and structured 'parts' so agents can negotiate capabilities, track task lifecycle, and return machine-readable artifacts. The upfront schema cost pays off in reliable parsing, validation, and observability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:49:39.643468+00:00— report_created — created