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

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_store [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:d:dependency_store [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Dependency Store ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Dependency Store is a controlled storage location that contains captured [[public:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]] and information required to identify, verify, organize, retrieve, and transfer them.
 +
 +The store may contain installation media, software packages, container images, provider packages, infrastructure source content, compliance artifacts, manifests, integrity values, and provenance information.
 +
 +A Dependency Store supports [[public:99_annexes:annex-b-terms-and-definitions:d:dependency_capture|Dependency Capture]] by providing a managed destination for dependency content and associated records.
 +
 +Within Crucible, the Dependency Store may initially use a host filesystem location and may later use an index, manifest, database, repository service, or other controlled representation without changing its architectural purpose.
 +
 +===== Definition =====
 +
 +//controlled storage location containing captured dependencies and information required to identify, verify, organize, retrieve, and transfer them//
 +
 +===== Source =====
 +
 +Generalized from package repositories, artifact stores, dependency caches, supply-chain repositories, and disconnected-operation usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +A Dependency Store differs from a package repository or container registry because it may contain several classes of Dependency and supporting evidence within one managed collection.
 +
 +The storage technology does not define the concept. A filesystem directory, repository service, object store, or database-backed service may realize a Dependency Store.
 +
 +===== Example =====
 +
 +A Crucible Dependency Store contains operating-system installation media, downloaded packages, compliance findings, container images, provider packages, and a manifest identifying the captured content.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>