Prevent interface changes from breaking consumers on a different release cycle

Ajwain is exploring API and Contract Assurance to give coding agents the compatibility rules for a change, then independently assess the changed interface against producer code, contract definitions, supported consumers, and tests before release.

Define compatibility around how producers and consumers actually release

A continuously deployed internal service and an application installed in customer environments cannot use the same assumptions about coordinated change. Compatibility depends on which consumer versions remain supported, when breaking changes are permitted, and what migration path is required.

API and Contract Assurance would make those rules available while an interface or schema change is implemented, then apply them again during review and CI. The team would continue to own supported versions, approved breaking changes, and release decisions.

Trace a contract change to the consumers that depend on it

Changing a required field, removing an enum value, or renaming an event can leave the producer valid while an older client or downstream service fails. The relevant impact may appear in an API definition, generated client, consumer repository, contract test, or migration requirement.

The proposed evaluation would connect the changed interface or schema to the consumers and versions examined. It would identify what could break, which information is missing, and whether the change needs a correction, version boundary, or migration step.

Make the compatibility decision reviewable before release

Each finding would show the applicable compatibility rule, the contract change, the consumer version or repository examined, and any generated client or test evidence that supports the result. Missing consumer information would remain visible instead of becoming an assumption.

Existing compatibility tools and contract tests would remain part of the workflow. Ajwain is intended to use the applicable rule and producer-consumer context alongside their results to show whether the change needs correction, a version boundary, migration work, or a reviewer decision.

See whether Ajwain can surface a consumer break before release

Use a past or current interface change involving an independently released consumer. Bring the contract, relevant repositories, and compatibility rule to assess whether a focused proof of concept identifies the known break or migration need before release.

Discuss a contract review problem