Classify objects by recovery and retention requirements
A broad expiry rule would remove the only copy of finalized reports.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Data lifecycle
Estimated field mix
- Storage systems50%
- Cloud infrastructure30%
- Site reliability20%
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.
Acceptance criteria
- Distinguish authoritative, reproducible, and temporary objects.
- Attach minimum retention and recovery requirements.
- Block lifecycle proposals for unclassified objects.
Implementation constraints
- Retention requirements are scenario inputs, not legal advice.
Verification to include
- Allow expiry of a declared temporary object.
- Block deletion of an authoritative unclassified report.
Deliverables
- Object lifecycle classification.
Rollout and recovery
Start with temporary classes only; preserve unknown objects.
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.