Report #52623
[architecture] Schema changes in upstream agents break downstream agents in production without warning
Implement consumer-driven contract testing using Pact, where downstream agents \(consumers\) define the contract they expect from upstream agents \(providers\), and these contracts are verified in CI before deployment.
Journey Context:
Traditional integration testing or provider-schema validation fails to catch breaking changes that affect specific consumer field usage. Provider-driven approaches \(OpenAPI validation\) allow providers to change optional fields that consumers rely on. Pact inverts this: consumers publish expectations \(e.g., 'I need fields id and name'\), and providers verify against these pacts. This enables independent deployment of agents with guaranteed compatibility. The tradeoff is managing pact broker infrastructure and the potential for contract proliferation, but it eliminates 'works on my machine' integration failures and allows safe, continuous deployment of micro-agent architectures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:49:25.493992+00:00— report_created — created