Save drafts without overwriting a second browser tab
A requester edits quantities in one tab and the explanation in another. Background autosave overwrites whichever tab saved first.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Optimistic concurrency · Draft recovery · State machines
Estimated field mix
- Frontend80%
- 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
The fictional Beacon operations team buys equipment through a browser form. Finance checks totals, departments, and quotes. Scope is one currency per request and an approval API contract; payments and accounting integration are excluded.
Setup prerequisites
- Synthetic department and cost-center directory
- Draft, submission, and approval API fixtures
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Autosave includes the loaded revision and serializes local writes.
- Conflicts pause autosave and offer reload or a reviewable copy of local edits.
- Navigating away with unsaved changes triggers a meaningful warning where supported.
Implementation constraints
- Never merge money fields automatically; preserve local edits for explicit conflict resolution.
Verification to include
- Save normally and verify the saved indicator follows the acknowledged revision.
- Race two tabs, then fail recovery fetch; local edits remain and autosave stays paused.
Deliverables
- Revision-aware draft coordinator and two-tab conflict reproduction
Rollout and recovery
Pilot manual saves before autosave; disable autosave without changing stored drafts if conflicts rise.
Value of the work
For the engineer: Practice form modeling, exact totals, revision handling, and collaboration under failure.
For the team: Inspect whether a developer protects business workflows from duplicate, lost, or misleading submissions.
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.