Normalize object inventory units and ownership labels
Inventory exports mix byte counts, rounded sizes, and missing owners.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Data normalization
Estimated field mix
- Data engineering60%
- Cloud infrastructure40%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Use bytes as the canonical size unit.
- Separate unknown owners from shared infrastructure.
- Preserve inventory time and source identity.
Implementation constraints
- Use synthetic names without customer identifiers.
Verification to include
- Normalize mixed display units accurately.
- Reject negative sizes and report missing ownership.
Deliverables
- Inventory parser.
Rollout and recovery
Run read-only attribution before proposing lifecycle changes.
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.