Make the preference form submit the user’s explicit final choice
An autosave race restores a checked box after the user turns it off and navigates away.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Form state · Accessible interaction
Estimated field mix
- Frontend40%
- Privacy engineering30%
- Accessibility30%
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
A fictional event workspace offers optional product announcements and operational booking messages. Its product policy treats these as separate purposes. A stale audience cache currently sends optional messages after a member opts out. The brief implements fictional preference rules and makes no legal-consent certification.
Setup prerequisites
- Create synthetic members, versioned notice text and two purpose-tagged message types.
- Use a fake dispatch provider with controllable queueing and acknowledgement; send no real messages.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Represent pending, saved and failed states without presenting an unconfirmed value as saved.
- Use version-aware updates so an older response cannot overwrite a newer choice.
- Keep controls keyboard-operable and associate errors with the affected purpose.
Implementation constraints
- Do not use preselected optional choices or obscured controls as a substitute for the declared interaction contract.
Verification to include
- Complete two opposite updates out of order and verify the latest accepted choice appears.
- Fail a save and navigate back; the form must distinguish persisted state from the unsaved attempt.
Deliverables
- Preference form state and out-of-order response tests
Rollout and recovery
Deploy with the versioned API; reverting the UI must not rewrite stored preference events.
Value of the work
For the engineer: Practice purpose modeling, versioned user choices, dispatch-time checks and consistency under retries.
For the team: Create an inspectable preference workflow that can be reviewed against a company-approved communication policy.
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.