Resolve deployment references to immutable artifact digests
The same release tag points to different bytes across environments.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Artifact integrity
Estimated field mix
- Developer tooling40%
- 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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Store the resolved digest with each deployment intent.
- Preserve the human-readable tag as metadata.
- Reject missing or ambiguous digest resolution.
Implementation constraints
- Synthetic registry manifests are sufficient.
Verification to include
- Resolve a stable release reference.
- Move its tag and detect changed identity.
Deliverables
- Artifact identity model.
Rollout and recovery
Introduce digest recording before enforcing immutable references.
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.