- WHY: align catalog 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
779 B
Markdown
22 lines
779 B
Markdown
# Catalog Contract Catalog
|
|
|
|
## Package
|
|
|
|
- `BuildingBlock.Catalog.Contracts`
|
|
|
|
## Contract Groups
|
|
|
|
- `Conventions`: transport-neutral request/response and envelope conventions.
|
|
- `Products`: transport-neutral product contract shapes.
|
|
- `Tags`: transport-neutral tag, tag type, and tag override contract shapes.
|
|
- `Abstractions`: marker abstraction for contract ownership.
|
|
- `Adapters`: protocol adapter boundaries.
|
|
- `Grpc`: gRPC contract shapes for adapter translation.
|
|
|
|
## Ownership Boundary
|
|
|
|
- This repository owns reusable catalog capability contracts.
|
|
- Contract metadata consumes `Core.Blueprint.Common.Contracts` and does not redefine Blueprint contracts.
|
|
- Persistence and transport implementations remain outside this package.
|
|
- Identity abstractions remain Thalos-owned.
|