public:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle

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:t:transfer_bundle [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle [2026/09/13 15:34] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Transfer Bundle ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +The Crucible Concept of Operations establishes the Transfer Bundle as the transferable collection produced within a [[public:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] and imported into a [[public:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]].
 +
 +A Transfer Bundle is a controlled collection of [[public:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[public:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], records, manifests, integrity information, and supporting [[public:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] assembled for transfer between environments.
 +
 +A Transfer Bundle may contain:
 +
 +  * Installation media
 +  * Software packages
 +  * Operating-system update packages
 +  * [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:c:container_image|Container Images]]
 +  * Provider-specific content
 +  * Infrastructure source content
 +  * Compliance Artifacts
 +  * Configuration
 +  * Records
 +  * Manifests
 +  * Integrity information
 +  * Supporting Evidence
 +  * A [[public:99_annexes:annex-b-terms-and-definitions:d:dependency_manifest|Dependency Manifest]]
 +
 +A Transfer Bundle facilitates controlled movement across an organizational, network, security, jurisdictional, or [[public:99_annexes:annex-b-terms-and-definitions:a:air_gap|Air Gap]] boundary while preserving the identity, integrity, organization, and [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] of its contents.
 +
 +Within [[public:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]], a Transfer Bundle may contain captured content from a [[public:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]]. A destination environment may import that content and use it to populate an internal software-package repository.
 +
 +The same Transfer Bundle retains its identity through:
 +
 +  * Creation
 +  * Transfer
 +  * Receipt
 +  * Integrity verification
 +  * Import
 +
 +The source phrases **artifact export package** and **artifact import package** describe the Transfer Bundle from the perspective of its creation or import. They do not identify separate transferable objects.
 +
 +===== Definition =====
 +
 +//controlled collection of [[public:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[public:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], records, manifests, integrity information, and supporting [[public:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] assembled for transfer between environments//
 +
 +===== Source =====
 +
 +[[private:05-crusible:99-annexes:annex-b:cr-002|Crucible Concept of Operations, Version 1.0]], Sections 2.1, 3.3, and 3.4.
 +
 +The Crucible Concept of Operations states that Crucible produces a compressed Transfer Bundle containing captured Dependencies and compliance findings within a connected enclave. The disconnected enclave imports the same bundle and uses its contents to populate an internal software-package repository.
 +
 +The ConOps also identifies the enclave operator as the actor that imports transferred dependency and Evidence bundles into a Disconnected Environment.
 +
 +This definition formalizes the ConOps concept without treating **package** and **Transfer Bundle** as separate names for the same architectural subject.
 +
 +===== Note =====
 +
 +A Transfer Bundle may use:
 +
 +  * A compressed archive
 +  * Removable media
 +  * An object-store representation
 +  * A repository export
 +  * Another controlled representation
 +
 +The representation of a Transfer Bundle does not change its identity as the controlled collection transferred between environments.
 +
 +Creating a Transfer Bundle does not by itself constitute [[public:99_annexes:annex-b-terms-and-definitions:t:transfer_authorization|Transfer Authorization]].
 +
 +Applicable review, approval, inspection, release, transfer, integrity-verification, and import processes govern movement across the applicable [[public:99_annexes:annex-b-terms-and-definitions:t:transfer_boundary|Transfer Boundary]].
 +
 +[[public:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle_integrity|Transfer Bundle Integrity]] governs the completeness of the Transfer Bundle and the protection of its contents from unauthorized addition, removal, or modification.
 +
 +A Transfer Bundle may contain software packages, but a Transfer Bundle is not itself a software package.
 +
 +===== Example =====
 +
 +[[public:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] assembles operating-system update packages, installation media, Container Images, infrastructure repositories, compliance Evidence, integrity values, and a Dependency Manifest into one Transfer Bundle for controlled transfer and import into an [[public:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]].
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>