Report #63699
[architecture] Silent schema drift between agents causing downstream parsing failures and hallucinated field interpretations
Enforce JSON Schema Draft 2020-12 with 'additionalProperties': false and semantic versioning in the $id URI; reject messages that fail validation at the ingress of each agent and emit structured schema violation telemetry
Journey Context:
Without strict validation, agents tolerate partial schema matches, leading to 'polyfill' hallucinations where downstream agents invent meaning for ambiguous fields. The 'additionalProperties': false guard forces explicit contract evolution rather than implicit extension. Versioning in $id \(e.g., https://example.com/schemas/agent-foo/v2\) prevents blue-green deployment collisions when agents roll out at different speeds. Alternatives like protobuf are binary-efficient but sacrifice the debuggability required for text-native LLM chains.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:24:29.818125+00:00— report_created — created