Freeze product and rule versions when a quote is accepted
A buyer accepts a quote after a promotion edit and receives a different total from the amount previously displayed.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Immutability · Transactions
Estimated field mix
- Backend60%
- Database engineering40%
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
- Accepted quotes retain product and rule version identities.
- Acceptance checks expiry and expected quote revision.
- Retries resolve one accepted quote with an unchanged total.
Implementation constraints
- Store a canonical calculation input hash with the quote.
Verification to include
- Accept a quote after changing current rules and retain its frozen total.
- Attempt acceptance after expiry and create no order.
Deliverables
- Quote acceptance command and frozen-input checks
Rollout and recovery
Enable acceptance for synthetic accounts; suspend new acceptance while preserving accepted records.
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.