Track notification and cache cleanup separately from the primary profile row
The operation reports success after deleting the database row even though a notification snapshot and cache entry still show the member’s details.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Workflow modeling · Partial failure
Estimated field mix
- Privacy engineering40%
- Distributed systems30%
- Backend30%
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.
- RDELETE-101 · Separate profile removal from leaving one organization
- RDELETE-102 · Verify the current member before accepting profile removal
- RDELETE-103 · Make repeated removal requests return the same active operation
- RDELETE-104 · Stop new profile-derived writes after removal begins
- RDELETE-105 · Remove profile documents from search using the removal generation
Acceptance criteria
- Track required locations with independent pending, confirmed and failed states.
- Differentiate already absent from unavailable or unauthorized provider responses.
- Advance overall completion only when the declared required locations satisfy the policy.
Implementation constraints
- The location registry is versioned for each operation so a later implementation change cannot silently rewrite its promised scope.
Verification to include
- Fail cache cleanup after database removal and verify a partial state with a retryable location.
- Return an authorization error from notifications and confirm it cannot be counted as confirmed absence.
Deliverables
- Location progress model and partial-cleanup fixtures
Rollout and recovery
Enable adapters one at a time in the local exercise; unsupported locations remain explicitly unresolved.
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.