Restore the right reply draft when switching tickets
Agents alternate between conversations while checking orders. The editor resets on every switch, and one experimental fix restored a draft into the wrong customer thread.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- State persistence · Privacy · Storage
Estimated field mix
- Frontend60%
- Privacy engineering40%
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
- Draft keys include organization, signed-in agent, and ticket.
- Returning to a ticket restores its text without copying it to another conversation.
- Sign-out clears local drafts; storage refusal leaves editing usable with a persistence notice.
Implementation constraints
- Use synthetic text and never record draft content in analytics.
Verification to include
- Write different drafts on two tickets, switch repeatedly, and reload in the same account.
- Switch organizations and simulate quota failure; no prior-account draft appears and typing still works.
Deliverables
- Scoped draft store and account-switch regression coverage
Rollout and recovery
Start with session-scoped storage; disable persistence and retain the in-memory editor if corruption is reported.
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.