c149695569
- 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
15 lines
530 B
C#
15 lines
530 B
C#
using BuildingBlock.Catalog.Contracts.Conventions;
|
|
|
|
namespace BuildingBlock.Catalog.Contracts.Responses;
|
|
|
|
/// <summary>
|
|
/// Transport-neutral catalog product response contract.
|
|
/// </summary>
|
|
/// <param name="Envelope">Contract envelope metadata.</param>
|
|
/// <param name="ProductId">Product identifier in catalog capability scope.</param>
|
|
/// <param name="DisplayName">Product display name.</param>
|
|
public sealed record ProductContractResponse(
|
|
CatalogContractEnvelope Envelope,
|
|
string ProductId,
|
|
string DisplayName);
|