Hide customer details in scheduling conflict responses
A failed reschedule currently returns the target booking object, exposing the name and contact information of its owner.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Privacy · Response schemas
Estimated field mix
- Privacy engineering50%
- Backend30%
- API design20%
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
- ABOOK-107 · Calculate the cancellation window from the booked service policy
Acceptance criteria
- Conflict responses contain only code and requested slot identity.
- Internal logs omit customer contact fields.
- Successful owners still receive their own booking projection.
Implementation constraints
- Use explicit response schemas instead of deleting selected fields.
Verification to include
- Check an owner's successful reschedule response.
- Force a conflict and assert another customer's fields appear nowhere in response or log.
Deliverables
- Sanitized conflict schema and disclosure regression
Rollout and recovery
Deploy response shaping first; revert only with the same restricted projection.
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.