dido:99_annexes:annex-b-terms-and-definitions:d:dependency_manifest

Differences

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

Link to this comparison view

dido:99_annexes:annex-b-terms-and-definitions:d:dependency_manifest [2026/07/13 12:33] – created nick_didodido:99_annexes:annex-b-terms-and-definitions:d:dependency_manifest [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 5: Line 5:
 ===== Discussion ===== ===== Discussion =====
  
-A Dependency Manifest is a machine-processable record that identifies the [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]] associated with a defined build, deployment, artefact, environment, or transfer bundle.+A Dependency Manifest is a machine-processable record that identifies the [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]] associated with a defined build, deployment, artifact, environment, or transfer bundle.
  
-The manifest may record dependency names, versions, types, source locations, integrity values, licenses, provenance, relationships, capture times, storage locations, and consuming artefacts or processes.+The manifest may record dependency names, versions, types, source locations, integrity values, licenses, provenance, relationships, capture times, storage locations, and consuming artifacts or processes.
  
 A Dependency Manifest supports verification, comparison, transfer, import, audit, and reproduction by making the captured dependency set explicit. A Dependency Manifest supports verification, comparison, transfer, import, audit, and reproduction by making the captured dependency set explicit.
Line 15: Line 15:
 ===== Definition ===== ===== Definition =====
  
-//machine-processable record that identifies the dependencies associated with a defined build, deployment, artefact, environment, or transfer bundle//+//machine-processable record that identifies the dependencies associated with a defined build, deployment, artifact, environment, or transfer bundle//
  
 ===== Source ===== ===== Source =====
  
-Generalized from software bills of materials, package manifests, dependency lock files, supply-chain records, and artefact inventories and specialized for the Crucible architecture and operational model.+Generalized from software bills of materials, package manifests, dependency lock files, supply-chain records, and artifact inventories and specialized for the Crucible architecture and operational model.
  
 ===== Note ===== ===== Note =====
Line 29: Line 29:
 ===== Example ===== ===== Example =====
  
-A Crucible Dependency Manifest records the installation medium, operating-system packages, provider packages, container images, infrastructure repository revisions, compliance artefacts, and integrity values included in a Transfer Bundle.+A Crucible Dependency Manifest records the installation medium, operating-system packages, provider packages, container images, infrastructure repository revisions, compliance artifacts, and integrity values included in a Transfer Bundle.
  
 ---- ----
  • dido/99_annexes/annex-b-terms-and-definitions/d/dependency_manifest.1783971217.txt.gz
  • Last modified: 2026/07/13 12:33
  • by nick_dido