Inventory every storage location used by one support attachment
Removing the primary upload leaves its thumbnail and a cached diagnostic preview behind.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Data mapping · Storage lifecycle
Estimated field mix
- Privacy engineering60%
- Storage systems40%
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 support service keeps uploaded diagnostic files indefinitely. The exercise policy expires attachments 30 days after case closure, while a separately authorized investigation hold pauses removal. These are invented product rules, not legal advice or compliance certification.
Setup prerequisites
- Create synthetic cases, attachment metadata and a fake object store with controllable failures.
- Use an injected UTC clock and an authorized operator fixture; no real support uploads are needed.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- List primary object, derived previews, metadata and any backup copy in a bounded data-flow inventory.
- Assign an owner and retention behavior to each location.
- Mark unknown or external copies explicitly instead of declaring removal complete.
Implementation constraints
- Use the fictional architecture and local adapters; do not discover or copy real customer data.
Verification to include
- Trace one synthetic upload through each declared location.
- Add an unknown derived location and verify the inventory marks coverage incomplete.
Deliverables
- Attachment lifecycle map and location registry
Rollout and recovery
Review the registry before wiring purge adapters; new derived stores require an inventory update.
Value of the work
For the engineer: Practice temporal policy, deletion races, exception authority and truthful recovery reporting.
For the team: Develop inspectable retention behavior that a company can review against its own approved data 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.