Report #66024
[architecture] Updating Agent A's output format breaks Agent B, C, D which consume it, causing production outages during rolling deployments
Implement consumer-driven contract tests and semantic versioning for inter-agent schemas; support backward-compatible schema evolution \(additive changes only\) with deprecation windows
Journey Context:
Unlike microservices where you control both sides, agent teams often work independently. Consumer-driven contracts \(Pact-style testing\) ensure upstream agents don't break downstream expectations. The alternative is centralized schema registries \(Avro/Protobuf style\), but LLM outputs are semi-structured. Practical approach: JSON Schema with 'additionalProperties: false' during development, relaxed in production with monitoring for schema drift. Version negotiation \(Accept-Schema-Version headers\) allows gradual migration without big-bang deployments.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T17:18:18.912359+00:00— report_created — created