Reject promotion of artifacts with unresolved policy findings
A failed scan is treated like a scan with no findings.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Policy design
Estimated field mix
- Security50%
- Developer tooling30%
- 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.
Acceptance criteria
- Distinguish passed, failed, missing, and stale checks.
- Bind check results to artifact and policy versions.
- Keep unresolved required checks blocking.
Implementation constraints
- Fixture scan results are not real vulnerability evidence.
Verification to include
- Promote a fixture with complete checks.
- Reject unavailable or stale check results.
Deliverables
- Promotion policy evaluator.
Rollout and recovery
Run advisory comparisons before enforcement.
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.