Protect rollback artifacts from registry retention cleanup
A cleanup job deletes the last known usable release.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Retention · Recovery
Estimated field mix
- Storage systems40%
- Site reliability30%
- Cloud infrastructure30%
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 application team deploys mutable image tags and cannot reliably identify the artifact running during an incident.
Setup prerequisites
- Author synthetic artifact manifests and a local registry double; do not pull or execute untrusted images.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BARTIF-101 · Resolve deployment references to immutable artifact digests
- BARTIF-102 · Record build inputs without exposing build secrets
- BARTIF-103 · Reject promotion of artifacts with unresolved policy findings
- BARTIF-104 · Keep environment-specific settings outside immutable application bytes
- BARTIF-105 · Bind a promotion decision to current environment state
- BARTIF-107 · Withdraw a defective artifact without deleting incident history
Acceptance criteria
- Retain artifacts referenced by active and rollback revisions.
- Evaluate cleanup from current authoritative references.
- Produce a dry-run deletion set.
Implementation constraints
- Use only local synthetic artifacts.
Verification to include
- Identify unreferenced eligible artifacts.
- Keep an older digest referenced by a rollback plan.
Deliverables
- Reference-aware retention policy.
Rollout and recovery
Run dry-run review before local deletion.
Value of the work
For the engineer: Practice artifact identity, promotion policies, and release provenance.
For the team: Provide reproducible deployments and a clear path to withdraw defective artifacts.
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.