Pin service build inputs to immutable identities
A rebuild of an old commit picks up a newer base image and no longer reproduces the original runtime.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Reproducibility · Dependency management
Estimated field mix
- Platform engineering70%
- Developer tooling30%
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
- Pin the base image digest and dependency lockfile.
- Record compiler and build-tool versions.
- Fail the build when frozen dependency resolution changes the lockfile.
Implementation constraints
- Document the update procedure rather than permanently freezing vulnerabilities.
Verification to include
- Build twice from identical named inputs and compare artifact metadata.
- Change a pinned input and require a new provenance record.
Deliverables
- Pinned build definition
Rollout and recovery
Introduce pinned builds for new artifacts; retain old digest references for rollback.
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.