Clear a shared device without dropping pending work invisibly
Two technicians share a tablet between shifts. Sign-out currently leaves cached addresses for the next user, but blindly deleting storage would also erase unsynced repairs.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Privacy · Account isolation · Data lifecycle
Estimated field mix
- Privacy engineering60%
- Mobile40%
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 Vale facilities team services equipment in basements with poor reception. Technicians receive assigned work orders, record checks, and attach synthetic equipment photos. The practice app uses an on-device database and a stub sync service; background location tracking is excluded.
Setup prerequisites
- Synthetic work orders and a revisioned sync contract
- An emulator with controllable connectivity and app lifecycle
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- FIELD-102 · Commit a completed checklist item before showing it saved
- FIELD-101 · Tell technicians which work orders are available offline
- FIELD-103 · Make inspection inputs usable with large text
- FIELD-104 · Keep photo evidence attached after the app is suspended
- FIELD-105 · Explain why a work order is not ready to finish
- FIELD-106 · Drain the sync queue without duplicating completed visits
- FIELD-107 · Keep reassigned work from being silently completed offline
- FIELD-108 · Resume a large photo upload without restarting the whole queue
Acceptance criteria
- Sign-out reports pending work before an explicit discard or sync choice.
- Confirmed sign-out removes account-scoped database rows, staged files, and credentials from the usable app context.
- Signing in as a different technician cannot render or sync the prior account’s data.
Implementation constraints
- Document the limits of app-level deletion; do not claim forensic erasure or export data automatically.
Verification to include
- Sync all work, sign out, and sign in as another user; no previous records appear.
- Fail sync with pending attachments and choose cancel; preserve the current session and work without exposing it to another account.
Deliverables
- Shared-device sign-out flow and account-boundary tests
Rollout and recovery
Require this check before shared-device pilots; disable account switching if cleanup cannot be confirmed.
Value of the work
For the engineer: Practice durable local state, mobile lifecycle recovery, and conflict resolution in realistic offline workflows.
For the team: Review whether an engineer can protect field work through crashes, interrupted uploads, and reassignment.
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.