Bind provenance to source, builder, and exact artifact
A provenance file names a commit but is copied beside a different archive without detection.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Provenance · Supply-chain security
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
- Statement binds artifact digest, source revision, build recipe, and builder identity
- Verification recomputes the artifact digest
- Unknown statement fields are preserved or rejected by version policy
Implementation constraints
- Builder identity is a synthetic workload identity, not a person or authorship claim.
Verification to include
- Verify the matching artifact and statement.
- Swap artifact and source identities independently and confirm failure.
Deliverables
- Versioned provenance statement and verifier
Rollout and recovery
Require verified provenance for a single fixture channel first.
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.