Report why a cart missed a promotion without leaking contract terms
Sales wants to explain an unmet minimum quantity, but the current debug endpoint exposes every account's price rules.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Authorization · Explainability
Estimated field mix
- Security50%
- Backend30%
- API design20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional parts supplier combines contract prices with promotions. Sales needs repeatable quotes when rules change during checkout.
Setup prerequisites
- Create synthetic products and integer minor-unit prices.
- Implement a small local quote API.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- ARULE-101 · Define the supported promotion predicates without executable expressions
- ARULE-102 · Resolve overlapping promotions with an explicit tie-break policy
- ARULE-103 · Validate promotion date ranges before publishing drafts
- ARULE-104 · Freeze product and rule versions when a quote is accepted
- ARULE-106 · Keep negotiated account prices outside shared quote caches
Acceptance criteria
- Explain only rules visible to the requesting account.
- Show failed predicate names with permitted thresholds.
- Omit internal contract identifiers and unrelated rule matches.
Implementation constraints
- Build a dedicated explanation projection.
Verification to include
- Explain a visible minimum-quantity miss.
- Request explanation for an inaccessible contract and receive no rule details.
Deliverables
- Scoped pricing explanation endpoint
Rollout and recovery
Enable the projection for one synthetic sales role; disable debug routes on disclosure failure.
Value of the work
For the engineer: Practice deterministic rule evaluation, revision control and bounded execution.
For the team: Review explainable commercial rules without trusting opaque price changes.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.