Replay a pricing dispute from immutable quote inputs
Support receives a disputed total after three rule releases and cannot reproduce which calculation the buyer accepted.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Reproducibility · Auditability
Estimated field mix
- Backend70%
- Developer tooling30%
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
- ARULE-107 · Report why a cart missed a promotion without leaking contract terms
- ARULE-108 · Compare a draft pricing revision against a named quote corpus
- ARULE-109 · Publish a pricing revision with optimistic review protection
Acceptance criteria
- Replay selects the recorded evaluator and input versions.
- Report missing versions as unreproducible rather than guessing.
- Compare computed total and hash with the accepted record.
Implementation constraints
- Keep replay read-only and use fabricated customer data.
Verification to include
- Replay an accepted synthetic quote across later releases.
- Remove an available version in the test double and assert explicit failure.
Deliverables
- Read-only dispute replay and failure cases
Rollout and recovery
Expose replay to scoped support users; revoke access if provenance cannot be resolved.
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.