Show assignment conflicts without pretending a save worked
Two leads assign the same ticket within a second. One console displays its optimistic assignment forever even though the API rejected the stale revision.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Concurrency · Optimistic UI · API contracts
Estimated field mix
- Frontend70%
- API design30%
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
The fictional Alder support team handles billing and delivery conversations in a browser console. Agents keep several tickets open, share filtered queues, and work through unreliable office Wi-Fi. The API contract returns ticket revisions and cursor-based pages; work stays within the console and its test adapter.
Setup prerequisites
- A ticket-list and reply API contract to implement or stub
- Synthetic conversations across two organizations with revision conflicts
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Writes include the last observed ticket revision.
- A conflict restores authoritative assignment and explains the competing update.
- An older rollback cannot overwrite a newer confirmed assignment.
Implementation constraints
- The API remains authoritative; never automatically retry a stale assignment.
Verification to include
- Accept an assignment and verify the returned revision replaces the local one.
- Interleave two changes with a conflict arriving last; the newest authoritative owner remains visible.
Deliverables
- Revision-aware assignment flow and interleaving tests
Rollout and recovery
Enable for one team and inspect conflicts; fall back to confirmed saves if optimistic rollback proves unreliable.
Value of the work
For the engineer: Practice state ownership, asynchronous races, accessible interaction, and recovery in bounded changes.
For the team: Inspect how an engineer protects agent work and handles failures that interrupt support operations.
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.