Show acknowledged and unsaved procurement draft states
Failed autosaves look saved. Track acknowledgements without interrupting editing.
- Focused work estimate
- 2h 45m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Async state · Persistence
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
Fictional procurement team Northroom collects purchase requests in a browser form. Work uses local stubs and cannot place purchases.
Setup prerequisites
- Create synthetic categories and conditional request fields.
- Stub draft revisions and submission outcomes.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Saved means acknowledged revision
- Failure retains edits
- Late acknowledgement cannot mark newer edits saved
Implementation constraints
- Debouncing cannot establish revision ownership.
Verification to include
- Save then edit
- Resolve saves out of order
Deliverables
- Draft states and race tests
Rollout and recovery
Disable autosave and expose explicit save.
Value of the work
For the engineer: Practice state boundaries and form schema transitions.
For the team: Inspect how hidden obsolete data and duplicate requests are prevented.
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.