Report #2206
[architecture] Agents exchange handoff context as free-form prose and parse it with regex
Use typed envelopes—Pydantic models or JSON-Schema message parts—and validate at every handoff boundary; keep natural language only inside human-readable fields.
Journey Context:
Free-form text feels flexible, but small schema drift \(a list vs a string, missing field\) forces downstream agents to guess, causing silent failures. Google's A2A protocol formalizes this with Agent Cards, Tasks, Messages, and typed Artifacts. Structured envelopes cost an upfront schema tax but remove ambiguity, let you unit-test handoffs, and make tracing deterministic. This is the same reason function calling beats prompt parsing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T10:07:39.608831+00:00— report_created — created