Preview entitlement changes without creating pending work
Sales wants to preview next month's downgrade, but the current preview endpoint creates a schedule visible to the worker.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Pure functions · API design
Estimated field mix
- Backend70%
- API design30%
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 document service grants storage and collaboration rights from subscriptions. Support cannot explain why delayed events restore old limits.
Setup prerequisites
- Create a local subscription API with synthetic accounts.
- Understand transactions and UTC intervals.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Preview uses the same pure decision function as execution.
- Return affected features and effective-time assumptions.
- No schedule, outbox or audit mutation occurs on preview.
Implementation constraints
- Authorize account reads before computing the preview.
Verification to include
- Compare preview with a later applied synthetic change.
- Repeat preview and assert unchanged row counts; deny another account.
Deliverables
- Pure preview operation and nonmutation checks
Rollout and recovery
Expose preview behind a route flag; remove the route without touching schedules.
Value of the work
For the engineer: Practice temporal rules, concurrency and explainable API decisions.
For the team: Review whether entitlement changes preserve customer access and produce supportable decisions.
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.