Report #24831
[architecture] Silent schema drift when Agent A outputs unstructured text but Agent B expects structured JSON
Enforce JSON Schema Draft 2020-12 at every agent boundary with strict validation \(additionalProperties: false\) and reject payloads that fail validation before they reach the consumer agent.
Journey Context:
Teams often start with 'smart' agents that 'just figure it out,' but LLMs are non-deterministic and will omit fields, hallucinate keys, or change types. Soft validation \(coercion\) creates Heisenbugs that only appear in production under load. The alternative—loose typing—works for 95% of cases but fails catastrophically on edge cases \(e.g., date strings parsed as math\). Strict schema enforcement with immediate failure \(fail-fast\) forces upstream agents to correct their output, creating a tight feedback loop and preventing error propagation down the chain.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T20:05:29.893012+00:00— report_created — created