Withdraw a defective artifact without deleting incident history
Deleting a bad image makes historical deployment records impossible to inspect.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Lifecycle management
Estimated field mix
- Platform engineering40%
- Security40%
- 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 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
Acceptance criteria
- Mark the digest withdrawn with reason and actor.
- Block new promotion of withdrawn artifacts.
- Preserve manifests and prior deployment references.
Implementation constraints
- Withdrawal is append-only state, not evidence deletion.
Verification to include
- Withdraw a synthetic defective artifact.
- Reject new promotion while retaining historical reads.
Deliverables
- Artifact withdrawal workflow.
Rollout and recovery
Withdraw before cleanup; use a separate approved retention policy.
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.