- 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
22 lines
823 B
Markdown
22 lines
823 B
Markdown
# Inventory Contract Catalog
|
|
|
|
## Package
|
|
|
|
- `BuildingBlock.Inventory.Contracts`
|
|
|
|
## Contract Groups
|
|
|
|
- `Conventions`: transport-neutral request/response and envelope conventions.
|
|
- `Requests`: capability request shapes for inventory use cases.
|
|
- `Responses`: capability response shapes for inventory use cases.
|
|
- `Abstractions`: marker abstractions for inventory contract ownership.
|
|
- `Adapters`: protocol adapter boundaries.
|
|
- `Grpc`: gRPC contract shapes for adapter translation.
|
|
|
|
## Ownership Boundary
|
|
|
|
- This repository owns inventory capability contracts only.
|
|
- Contract metadata consumes `Core.Blueprint.Common.Contracts` and does not redefine Blueprint contracts.
|
|
- Implementation details stay in furniture-service, furniture-bff, or furniture-dal.
|
|
- Identity abstractions are out of scope and remain Thalos-owned.
|