noCV
ARULE-103 · Constrain rule input

Validate promotion date ranges before publishing drafts

Practice briefBugFoundational

A promotion with its end before its start passes draft review and can never apply.

Focused work estimate
1h + prerequisites
Priority in the scenario
Medium
Engineering practice
Validation · Temporal rules

Estimated field mix

  • Backend100%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

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

  • Require offset-bearing UTC-normalizable dates.
  • Reject empty and reversed ranges at publication.
  • Display validation paths without raw rule documents in logs.

Implementation constraints

  • Use half-open intervals consistently.

Verification to include

  • Publish an adjacent pair of valid promotions.
  • Reject reversed, missing-offset and empty intervals.

Deliverables

  • Publication date guard

Rollout and recovery

Deploy guard for unpublished drafts; preserve existing published versions.

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.