Model overlapping technician availability as half-open intervals
Adjacent visits are rejected as overlapping, while a visit completely containing another can pass a naive endpoint check.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- SQL · Interval reasoning
Estimated field mix
- Backend50%
- Database engineering50%
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
- Adjacent end and start boundaries do not conflict.
- Contained and partially overlapping intervals conflict.
- Conflict checks include the technician's organization.
Implementation constraints
- Document the half-open interval convention in the query.
Verification to include
- Check adjacent, contained and identical intervals.
- Try the same technician identifier in another organization and deny access.
Deliverables
- Overlap query and interval matrix
Rollout and recovery
Shadow-check overlap decisions; restore the old route if new conflicts need review.
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.