Promote only artifacts whose evidence set reconciles
A package is promoted after signature verification even though its inventory belongs to an earlier build.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Release gates · Integrity · Policy validation
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 command-line product publishes local package archives. Builds contain timestamps, checksums are copied without provenance, and cleanup can delete the only rollback artifact. Use generated source trees, ephemeral development signing keys, and local object storage; no public registry or production key is supplied.
Setup prerequisites
- Content hashing
- Archive formats
- Release metadata
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Gate binds artifact, provenance, inventory, signature, and policy versions
- Every component references the same artifact digest
- Missing or conflicting metadata blocks promotion with exact reasons
Implementation constraints
- This verifies release metadata, not candidate Outcome Evidence or ownership.
Verification to include
- Promote one complete matching fixture set.
- Mix inventory, signature, and provenance from neighboring builds and reject each case.
Deliverables
- Artifact evidence-set gate and mismatch matrix
Rollout and recovery
Run the gate in report-only mode before making it mandatory.
Value of the work
For the engineer: Practice reproducible artifacts, provenance validation, signing-key isolation and retention safety.
For the team: Review a supply path that can trace, verify, retain, and revoke artifacts without relying on mutable names.
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.