Retain rollback artifacts while bounding storage growth
Age-only cleanup removes the last compatible rollback artifact for a supported release line.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Retention · Object storage · Recovery
Estimated field mix
- DevOps60%
- Storage systems40%
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 command-line product publishes local package archives. Builds contain timestamps, checksums are copied without provenance, and cleanup can delete the only rollback artifact. Use generated source trees, ephemeral development signing keys, and local object storage; no public registry or production key is supplied.
Setup prerequisites
- Content hashing
- Archive formats
- Release metadata
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- DART-101 · Make archive bytes reproducible from the same source manifest
- DART-102 · Generate a dependency inventory from resolved inputs
- DART-103 · Bind provenance to source, builder, and exact artifact
- DART-104 · Keep signing keys outside the build workspace
- DART-105 · Promote only artifacts whose evidence set reconciles
- DART-106 · Prevent a mutable channel from changing an approved artifact
Acceptance criteria
- Retention protects active, rollback, held, and investigation-referenced digests
- Deletion plan is deterministic and reviewable before mutation
- Partial deletion resumes by immutable digest
Implementation constraints
- Use local object storage and synthetic artifact bytes; never delete undeclared objects.
Verification to include
- Plan and execute cleanup while retaining every protected digest.
- Interrupt halfway and replay; add an unknown reference and keep it unresolved.
Deliverables
- Artifact retention planner and interrupted cleanup drill
Rollout and recovery
Run plan-only mode before enabling scoped fixture deletion.
Value of the work
For the engineer: Practice reproducible artifacts, provenance validation, signing-key isolation and retention safety.
For the team: Review a supply path that can trace, verify, retain, and revoke artifacts without relying on mutable names.
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.