Bound pricing work for a cart with many matching rules
An unusually broad rule set makes checkout evaluate thousands of predicates per item and blocks unrelated quotes.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Resource budgets · Complexity
Estimated field mix
- Performance engineering50%
- Backend50%
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.
Acceptance criteria
- Set explicit cart, rule-count and predicate-work limits.
- Reject over-budget requests before partial quote publication.
- Return a bounded-work error distinct from invalid pricing.
Implementation constraints
- Choose limits from a repeatable local synthetic workload and document conditions.
Verification to include
- Measure work counters for 100 items and 200 rules.
- Exceed each limit and verify no accepted quote is created.
Deliverables
- Evaluation budget and reproducible workload
Rollout and recovery
Canary limits in observation mode; lower admitted work or restore prior limits on regressions.
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.