Poesis
Usage / Use case
Review a breaking API contract change
Identify affected consumers and inspect compatibility evidence before accepting an interface change and migration conditions.
API product owner / Enterprise Architect / Application owner
Platform
What serves this use case
No platform coverage declared.
Values
Values composed with this use case
- Value Planned
Predictable evolution of shared interfaces
Coordinate contract changes and consumer migration against explicit compatibility evidence and retirement prerequisites.
Realized through Use cases(2)
Pains
Pain points
- Pain point Planned
A shared API changes before all affected consumers and migration conditions are known.
Uncoordinated upgrades and deprecations disrupt dependent services and force emergency compatibility work.
Experienced by Actor types(3)
Addressed through Use cases(2)