Detect orphan holds without changing confirmed appointments
A simulated outage leaves holds whose expiry jobs were never dispatched; operations needs a bounded reconciliation command.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Reconciliation · Optimistic concurrency
Estimated field mix
- Backend50%
- Database engineering30%
- Site reliability20%
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.
- ABOOK-101 · Normalize maintenance-slot requests to explicit UTC intervals
- ABOOK-102 · Model overlapping technician availability as half-open intervals
- ABOOK-104 · Reserve one active hold for a contested maintenance slot
- ABOOK-105 · Expire holds without cancelling a booking confirmed at the boundary
- ABOOK-106 · Reschedule a visit without releasing its old slot prematurely
Acceptance criteria
- Scan expired held rows with cursor checkpoints.
- Release only rows still held at the checked version.
- Report confirmed rows skipped after concurrent change.
Implementation constraints
- Use dry-run by default and limit each batch.
Verification to include
- Reconcile an expired orphan and resume from a checkpoint.
- Confirm between scan and update and verify the booking survives.
Deliverables
- Orphan-hold reconciler and race check
Rollout and recovery
Dry-run a bounded window; stop reconciliation and retain checkpoints if unexpected skips grow.
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.