Reject stale stock updates without losing drafts
Two buyers edit the same row and the second overwrites the first. Handle revision conflicts.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Concurrency · HTTP
Estimated field mix
- Frontend60%
- API design40%
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 supplier Reedworks uses a browser inventory table. Quantities are planning records, not live warehouse instructions.
Setup prerequisites
- Create synthetic SKUs with revisions and nullable quantities.
- Implement a local paginated adapter with conditional updates.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Saves include expected revision
- Conflict preserves draft and current value
- Resubmission requires reconciliation
Implementation constraints
- Never blindly retry conflicts.
Verification to include
- Accept matching revision
- Reject stale revision and inspect draft
Deliverables
- Conflict panel and adapter cases
Rollout and recovery
Gate editing while conflict handling is repaired.
Value of the work
For the engineer: Practice grid interaction and concurrent edit recovery.
For the team: Inspect how changes protect operator intent during partial failures.
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.