Define the supported promotion predicates without executable expressions
Sales requested a formula textbox; evaluating arbitrary expressions would make quote behavior difficult to bound and audit.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Schema design · Input validation
Estimated field mix
- Backend60%
- API design20%
- Security20%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Allow explicit product, quantity and date predicates.
- Reject unknown operators and excessive nesting.
- Publish a schema with accepted and rejected examples.
Implementation constraints
- Treat rule documents as data; never evaluate source strings.
Verification to include
- Parse a quantity-band promotion.
- Reject a function expression and a nesting-limit violation.
Deliverables
- Promotion schema and parser cases
Rollout and recovery
Accept drafts only initially; disable new drafts if parser compatibility fails.
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.