Announce staffing conflicts without repeating the entire calendar
A revision conflict rerenders the grid and reads dozens of cells. Isolate a concise conflict message and resolution controls.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Live regions · Error handling
Estimated field mix
- Accessibility60%
- Frontend40%
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
Fictional studio Loom assigns editorial shifts. Build synthetic shifts and a local scheduling adapter; no real staff records are used.
Setup prerequisites
- Create synthetic shifts including overlaps and daylight-saving boundaries.
- Implement a local schedule revision adapter.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Conflict identifies affected shift
- Draft remains available
- Calendar content is not a live region
Implementation constraints
- Announcements must not reveal unrelated staff data.
Verification to include
- Trigger one conflict
- Retry failure and check announcement count
Deliverables
- Conflict status region
Rollout and recovery
Disable auto-refresh announcements if they repeat.
Value of the work
For the engineer: Practice focus models and accessible alternatives for spatial interfaces.
For the team: Inspect whether scheduling remains usable across input methods and failure states.
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.