Document restoration before approving local expiry rules
Cleanup reviewers need to understand which deleted artifacts can be recreated.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Low
- Engineering practice
- Runbooks
Estimated field mix
- Site reliability50%
- Cloud infrastructure30%
- Storage systems20%
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 analytics service stores exports and intermediate artifacts indefinitely. Finance sees a rising bill but engineers cannot explain which lifecycle policy is responsible.
Setup prerequisites
- Create synthetic object inventories and a local object-store double; author fictional unit prices as explicit assumptions.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BCOST-101 · Normalize object inventory units and ownership labels
- BCOST-102 · Model storage, requests, and transfer costs separately
- BCOST-103 · Classify objects by recovery and retention requirements
- BCOST-105 · Account for retrieval delay in colder storage proposals
- BCOST-104 · Simulate lifecycle transitions before object deletion
- BCOST-106 · Bound export retention per tenant without crossing ownership
- BCOST-107 · Reduce repeated downloads with integrity-aware caching
- BCOST-108 · Compare retention changes against rebuild workload and budget
- BCOST-109 · Add budget alerts that distinguish actual and forecast usage
Acceptance criteria
- Identify rebuild inputs and commands.
- State unrecoverable classes explicitly.
- Include the latest dry-run plan identity.
Implementation constraints
- Do not promise recovery without retained inputs.
Verification to include
- Rebuild an expired synthetic intermediate artifact.
- Reject expiry when required rebuild inputs are absent.
Deliverables
- Retention review checklist.
Rollout and recovery
Attach to policy proposals and re-review after input changes.
Value of the work
For the engineer: Practice cost attribution, lifecycle modeling, and safe retention controls.
For the team: Produce reviewable storage-cost options with recovery and data-retention consequences.
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.