Tombstone unreferenced blobs before physical deletion
Cleanup deletes bytes immediately when count reaches zero, leaving no recoverable decision record. Add a pending-deletion state.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Lifecycle · Data integrity
Estimated field mix
- Storage systems60%
- Database engineering40%
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
Fictional archive Moss deduplicates generated attachments across documents within each organization. Use local files and transactional metadata stubs.
Setup prerequisites
- Generate duplicate and unique local byte fixtures.
- Create synthetic document references across two organizations.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Zero references create tombstone
- Referenced blobs remain available
- Tombstone records eligibility time
Implementation constraints
- Tombstones describe metadata, not proof of physical erasure.
Verification to include
- Remove final reference
- Remove one of two references
Deliverables
- Tombstone transition and cases
Rollout and recovery
Pause physical deletion while retaining tombstones.
Value of the work
For the engineer: Practice reclamation races and explicit data-lifecycle guarantees.
For the team: Inspect whether storage cleanup avoids broken references and hidden retention.
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.