Stop new profile-derived writes after removal begins
The notification worker recreates a cached profile card while cleanup is deleting it.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Lifecycle coordination · Data minimization
Estimated field mix
- Privacy engineering50%
- Distributed systems30%
- Backend20%
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 collaboration product lets a member request removal of their personal profile. Search, notifications and cached displays retain copies after the primary row disappears. The exercise uses a documented product deletion policy and synthetic identities.
Setup prerequisites
- Create local profile, search-index and notification fixtures with controlled provider failures.
- Define synthetic members, organizations and a current-session authorization fixture.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Record a lifecycle boundary that profile-derived writers check before producing new copies.
- Define how already queued work is cancelled or rejected for the removal generation.
- Preserve required nonpersonal operational records without copying the removed profile into them.
Implementation constraints
- Use a generation or tombstone contract with explicit retention; do not keep the entire deleted profile inside a tombstone.
Verification to include
- Queue a notification before removal and release it afterward; no new profile copy may appear.
- Race an edit with removal and verify one declared outcome with no profile resurrection.
Deliverables
- Write barrier and profile-resurrection race tests
Rollout and recovery
Deploy the writer check before activating cleanup; stop new operations if a writer cannot honor it.
Value of the work
For the engineer: Practice distributed cleanup, identity scope, idempotency and accurate user-facing lifecycle states.
For the team: Produce a reviewable deletion workflow and copy inventory for adaptation to an approved company 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.