Review pricing engine type tenant vs party design
Table of Contents
This page is a capture in the deferred bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
What
(One paragraph: the idea.)
Why
(Motivation, problem being solved, related context.)
References
See also
PricingEngineType has a tenant_id foreign key but no party_id. Questions to resolve before the next pricing engine sprint:
- Should a pricing engine type be visible across an entire tenant or scoped to a party within the tenant? If it's party-scoped, add the FK; if tenant-scoped, document why.
- The current code defaults
tenant_idtoutility::uuid::tenant_id::system(). Is this intentional (system-wide types) or a placeholder? If a placeholder, switch to a well-known invalid sentinel and force callers to supply a real tenant.
Resolve during backlog refinement before pulling into a sprint.