Authorize release approval for the exact artifact
An approval made for one digest remains valid after the release record is edited to point at another artifact.
- Focused work estimate
- 6h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Authorization · Release governance · Audit
Estimated field mix
- DevOps60%
- Security40%
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 scheduling API is rebuilt separately for test, staging, and production-like local environments. The resulting images differ, release notes list the branch instead of the artifact, and rollback rebuilds old source with new dependencies. Use a local registry simulator and synthetic deployments; no cluster or customer traffic is supplied.
Setup prerequisites
- Artifact digests
- Release states
- Health checks
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Approval binds artifact digest, environment, policy version, and expiry
- Any bound-field change invalidates approval
- Requester cannot satisfy a required independent approval role
Implementation constraints
- Use synthetic identities and permissions; this is workflow authorization, not proof of code authorship.
Verification to include
- Approve and promote the exact eligible release.
- Change digest and replay the approval token, then verify denial and audit.
Deliverables
- Release approval boundary and replay tests
Rollout and recovery
Require explicit approval for the final simulated environment first.
Value of the work
For the engineer: Practice immutable promotion, release authority, compatibility gates, canaries, and rollback.
For the team: Review a delivery flow that can identify exactly what is running and restore a known artifact without rebuilding it.
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.