Return bookable slots in stable bounded pages
A busy service desk loads every future slot; several slots disappear from the second page when a new slot is inserted.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Pagination · API contracts
Estimated field mix
- API design60%
- Backend40%
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 equipment service books maintenance visits. Expiring checkout holds and reschedules occasionally double-book a technician.
Setup prerequisites
- Build synthetic technicians, slots and booking records.
- Use an injectable clock and separate clients for concurrency probes.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Order by start instant and opaque slot ID.
- Use a cursor bound to technician and date window.
- Enforce a maximum page size and bounded date range.
Implementation constraints
- Do not expose unassigned technicians outside the organization.
Verification to include
- Insert a slot between pages and inspect stable cursor progression.
- Reject an altered cursor scope and excessive range.
Deliverables
- Availability page contract and cursor tests
Rollout and recovery
Introduce cursor pagination alongside the old bounded endpoint; roll back its link.
Value of the work
For the engineer: Practice resource allocation, interval conflicts and durable workflows.
For the team: Review scheduling correctness and recovery before exposing scarce capacity.
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.