Simulate lifecycle transitions before object deletion
Operators cannot see which objects a new rule would affect.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Change safety · Integrity
Estimated field mix
- Cloud infrastructure40%
- Storage systems40%
- Security20%
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
- Produce a dry-run object set and byte total.
- Bind the plan to inventory and policy digests.
- Reject execution if the reviewed plan is stale.
Implementation constraints
- The exercise uses only a disposable local object store.
Verification to include
- Preview an eligible temporary set.
- Change policy inputs and reject the stale plan.
Deliverables
- Lifecycle dry-run planner.
Rollout and recovery
Require review of the exact plan; keep deletion disabled by default.
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.