public:99_annexes:annex-b-terms-and-definitions:d:dependency_capture

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:d:dependency_capture [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:d:dependency_capture [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Dependency Capture ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Dependency Capture is the controlled process of identifying, collecting, recording, and preserving the [[public:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]] used or required by a defined build, deployment, assessment, or operational process.
 +
 +The process may capture dependency content, identities, versions, source locations, integrity values, licensing information, provenance, and relationships to the process or artifact that consumed them.
 +
 +Dependency Capture supports reproducibility, supply-chain control, offline operation, auditability, and transfer into a [[public:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]].
 +
 +Within Crucible, Dependency Capture may collect installation media, operating-system packages, container images, provider packages, infrastructure repositories, and compliance evidence into a managed [[public:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]].
 +
 +===== Definition =====
 +
 +//controlled process of identifying, collecting, recording, and preserving the dependencies used or required by a defined process//
 +
 +===== Source =====
 +
 +Generalized from dependency management, software supply-chain management, reproducible-build practice, and disconnected-operation usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +Dependency Capture does not necessarily copy every external service or capability. The capture scope identifies which Dependencies can be preserved as transferable content and which require another form of representation or substitution.
 +
 +A complete Dependency Capture should preserve enough information to identify the captured content and relate it to the process or artifact that used it.
 +
 +===== Example =====
 +
 +During an Image Build, Crucible captures installation media, downloaded operating-system packages, compliance results, and associated metadata into a Dependency Store for later transfer into an air-gapped enclave.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>