Record image provenance without embedding build credentials
Operations can see a tag but cannot trace it to source revision, dependency lock hash or build run.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Supply chain · Provenance
Estimated field mix
- Platform engineering60%
- 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 reporting API is rebuilt separately for staging and production. Different dependency resolutions and mutable tags make incident rollback unreliable.
Setup prerequisites
- Create a tiny local HTTP service and nonprivileged image build.
- Use synthetic registries or provider fixtures; no production deployment.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Record source revision, input hashes and final image digest.
- Associate provenance with the exact artifact digest.
- Exclude environment values and registry tokens.
Implementation constraints
- Use a local provenance document for this exercise.
Verification to include
- Resolve a built digest to its source and lockfile hashes.
- Alter provenance digest and reject the mismatch.
Deliverables
- Artifact provenance manifest and verification command
Rollout and recovery
Attach provenance to new builds; refuse promotion when it cannot be verified.
Value of the work
For the engineer: Practice artifact identity, least privilege and reproducible delivery.
For the team: Review whether deployed bytes can be traced and rolled back reliably.
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.