Bound export retention per tenant without crossing ownership
One tenant's cleanup job selects similarly named exports belonging to another.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Authorization · Storage
Estimated field mix
- Security50%
- Storage systems30%
- Cloud infrastructure20%
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
- Scope inventory and policy evaluation by tenant identity.
- Use opaque object references rather than name prefixes alone.
- Audit planned and completed cleanup identities.
Implementation constraints
- Repository boundaries must enforce scope.
Verification to include
- Expire eligible exports for one tenant.
- Attempt cross-tenant cleanup and verify denial.
Deliverables
- Scoped retention evaluator.
Rollout and recovery
Trial on one synthetic tenant; stop on inventory discrepancies.
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.