Calculate archive storage growth from event size and retention assumptions
A budget proposal counts raw event bytes but omits index, replica and manifest overhead.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Capacity modeling · Cost reasoning
Estimated field mix
- System design50%
- 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 procurement platform keeps append-only action records. Operators want fast recent search and affordable old records without losing provenance or leaking tenant data.
Setup prerequisites
- Create synthetic audit events and local storage/search adapters.
- Use an explicit fictional retention policy, not legal advice.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Model events per day, average bytes and retention duration.
- Show raw, index and redundancy components separately.
- Label compression and growth factors as assumptions.
Implementation constraints
- Provide a small executable worksheet with no claimed measured savings.
Verification to include
- Calculate the baseline synthetic scenario.
- Double event volume and vary compression to show sensitivity.
Deliverables
- Storage-growth model
Rollout and recovery
Use the model for a reviewed budget proposal; update it after real storage measurements.
Value of the work
For the engineer: Practice storage tradeoffs, provenance and data-lifecycle decisions.
For the team: Review archive cost and retrieval guarantees before committing to infrastructure.
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.