- WHY: align inventory capability contracts with protocol-agnostic integration boundaries - WHAT: add contract conventions, grpc adapter surfaces, and blueprint descriptor consumption - RULE: enforce building-block to blueprint dependency direction
18 lines
671 B
Markdown
18 lines
671 B
Markdown
# Inventory Versioning Policy
|
|
|
|
## Policy
|
|
|
|
- Contract changes follow additive-first evolution.
|
|
- Breaking changes require a new major package version.
|
|
- Deprecated members should remain for at least one release cycle.
|
|
|
|
## Blueprint Compatibility
|
|
|
|
- Package descriptor metadata is implemented via `IBlueprintPackageContract` from `Core.Blueprint.Common.Contracts`.
|
|
- Inventory contracts consume Blueprint common contract primitives rather than redefining them.
|
|
|
|
## Compatibility Notes
|
|
|
|
- Consumer repositories (`furniture-service`, `furniture-bff`) should update contracts explicitly.
|
|
- Protocol adapters remain edge concerns; inventory contracts remain transport-neutral.
|