Model storage, requests, and transfer costs separately
A storage-only estimate ignores the cost of regenerating and downloading exports.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Cost modeling
Estimated field mix
- Cloud infrastructure100%
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
- Version explicit fictional unit-price assumptions.
- Calculate each cost component separately.
- Show unknown request or transfer volume.
Implementation constraints
- Do not present modeled savings as observed billing results.
Verification to include
- Reconcile a hand-calculated synthetic example.
- Refuse a total when a required unit conversion is ambiguous.
Deliverables
- Offline cost calculator.
Rollout and recovery
Keep original assumptions with every report.
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.