====== Pull Lock ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] ===== Discussion ===== A Pull Lock is a machine-processable record of the exact source revisions resolved and retrieved during a Crucible pull operation. A Pull Lock connects the source references in a [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Description]] to the immutable revision identifiers used in a particular pipeline execution. The record supports [[dido:99_annexes:annex-b-terms-and-definitions:v:version_pinning|Version Pinning]], [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] by preserving the relationship between requested source versions and retrieved source revisions. A Pull Lock may identify image, provisioning, infrastructure, application, compliance, or other repositories retrieved into a [[dido:99_annexes:annex-b-terms-and-definitions:p:pipeline_workspace|Pipeline Workspace]]. ===== Definition ===== //machine-processable record of the exact source revisions resolved and retrieved during a Crucible pull operation// ===== Source ===== Specialized from dependency lock files, source-resolution records, and reproducible-build usage for the Crucible architecture and operational model. ===== Note ===== A Pull Lock records resolved source revisions. It does not contain the complete retrieved source content. A later execution can compare its resolved revisions with the Pull Lock to detect changed inputs or reproduce the earlier source selection. ===== Example ===== A Crucible Description references tagged image and infrastructure repositories. The pull operation resolves both tags to exact Git commit identifiers and records those identifiers in a Pull Lock. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.