| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle [2026/07/19 07:23] – nick_dido | dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle [2026/07/19 07:30] (current) – [Source] nick_dido |
|---|
| ===== Discussion ===== | ===== Discussion ===== |
| |
| The [[====== Transfer Bundle ====== | The Crucible Concept of Operations establishes the Transfer Bundle as the transferable collection produced within a [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] and imported into a [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]]. |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] | A Transfer Bundle is a controlled collection of [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], records, manifests, integrity information, and supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] assembled for transfer between environments. |
| |
| ===== Discussion ===== | A Transfer Bundle may contain: |
| | |
| The [[dido:02-crusible:99-annexes:annex-b:cr-002|Crucible Concept of Operations, Version 1.0]] establishes the [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle|Transfer Bundle]] as the package produced within a [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] for controlled transfer and subsequent import into a [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]]. | |
| | |
| A Transfer Bundle is a controlled package of [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], records, manifests, integrity information, and supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] prepared for transfer between environments. | |
| | |
| The Transfer Bundle may contain: | |
| |
| * Installation media | * Installation media |
| * Software packages | * Software packages |
| | * Operating-system update packages |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] | * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:container_image|Container Images]] | * [[dido:99_annexes:annex-b-terms-and-definitions:c:container_image|Container Images]] |
| * Provider packages | * Provider-specific content |
| * Infrastructure source content | * Infrastructure source content |
| * Compliance Artifacts | * Compliance Artifacts |
| A Transfer Bundle facilitates controlled movement across an organizational, network, security, jurisdictional, or [[dido:99_annexes:annex-b-terms-and-definitions:a:air_gap|Air Gap]] boundary while preserving the identity, integrity, organization, and [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] of its contents. | A Transfer Bundle facilitates controlled movement across an organizational, network, security, jurisdictional, or [[dido:99_annexes:annex-b-terms-and-definitions:a:air_gap|Air Gap]] boundary while preserving the identity, integrity, organization, and [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] of its contents. |
| |
| Within [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]], a Transfer Bundle may contain captured content from a [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]] for import into a Disconnected Environment. | Within [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]], a Transfer Bundle may contain captured content from a [[dido: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: | The same Transfer Bundle retains its identity through: |
| * Import | * Import |
| |
| The terms **artifact export package** and **artifact import package** describe the Transfer Bundle from the perspective of its creation or import. They do not identify separate package types unless the controlling architecture explicitly defines different structures or identities. | 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 ===== | ===== Definition ===== |
| |
| //controlled package of [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], records, manifests, integrity information, and supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] prepared for transfer between environments// | //controlled collection of [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], records, manifests, integrity information, and supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] assembled for transfer between environments// |
| |
| ===== Source ===== | ===== Source ===== |
| |
| [[dido:02-crusible:99-annexes:annex-b:cr-002|Crucible Concept of Operations, Version 1.0]], Sections 3.3 and 3.4. | [[dido:02-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 introduces the Transfer Bundle as the package produced within a Connected Environment and imported into a Disconnected Environment. The ConOps also associates Dependencies, compliance findings, and supporting information with the Transfer Bundle. | 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. |
| |
| This definition generalizes the ConOps concept using established secure-transfer, disconnected-operation, archive-packaging, software-supply-chain, and configuration-management practices. | 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 ===== | ===== Note ===== |
| * A compressed archive | * A compressed archive |
| * Removable media | * Removable media |
| * An object package | * An object-store representation |
| * A repository export | * A repository export |
| * Another controlled representation | * Another controlled representation |
| |
| Packaging content into a Transfer Bundle does not by itself constitute [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_authorization|Transfer Authorization]]. | The representation of a Transfer Bundle does not change its identity as the controlled collection transferred between environments. |
| | |
| Applicable review, approval, inspection, release, transfer, integrity-verification, and import processes govern movement across the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_boundary|Transfer Boundary]]. | |
| | |
| [[dido: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. | |
| | |
| The Transfer Bundle may contain Artifacts that require separate approval, promotion, validation, or authorization before deployment or operational use. | |
| | |
| ===== Example ===== | |
| | |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] packages operating-system 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 [[dido: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>|Crucible Concept of Operations, Version 1.0]] establishes the [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle|Transfer Bundle]] as the package produced within a [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] for controlled transfer and subsequent import into a [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]]. | |
| | |
| A Transfer Bundle is a controlled package of [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], records, manifests, integrity information, and supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] prepared for transfer between environments. | |
| | |
| The Transfer Bundle may contain: | |
| | |
| * Installation media | |
| * Software packages | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:container_image|Container Images]] | |
| * Provider packages | |
| * Infrastructure source content | |
| * Compliance Artifacts | |
| * Configuration | |
| * Records | |
| * Manifests | |
| * Integrity information | |
| * Supporting Evidence | |
| * A [[dido: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 [[dido:99_annexes:annex-b-terms-and-definitions:a:air_gap|Air Gap]] boundary while preserving the identity, integrity, organization, and [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] of its contents. | |
| | |
| Within [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]], a Transfer Bundle may contain captured content from a [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]] for import into a Disconnected Environment. | |
| | |
| The same Transfer Bundle retains its identity through: | |
| | |
| * Creation | |
| * Transfer | |
| * Receipt | |
| * Integrity verification | |
| * Import | |
| | |
| The terms **artifact export package** and **artifact import package** describe the Transfer Bundle from the perspective of its creation or import. They do not identify separate package types unless the controlling architecture explicitly defines different structures or identities. | |
| | |
| ===== Definition ===== | |
| | |
| //controlled package of [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], records, manifests, integrity information, and supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] prepared for transfer between environments// | |
| | |
| ===== Source ===== | |
| | |
| [[<established-ConOps-reference-namespace>|Crucible Concept of Operations, Version 1.0]], Sections 3.3 and 3.4. | |
| | |
| The Crucible Concept of Operations introduces the Transfer Bundle as the package produced within a Connected Environment and imported into a Disconnected Environment. The ConOps also associates Dependencies, compliance findings, and supporting information with the Transfer Bundle. | |
| | |
| This definition generalizes the ConOps concept using established secure-transfer, disconnected-operation, archive-packaging, software-supply-chain, and configuration-management practices. | |
| | |
| ===== Note ===== | |
| | |
| A Transfer Bundle may use: | |
| | |
| * A compressed archive | |
| * Removable media | |
| * An object package | |
| * A repository export | |
| * Another controlled representation | |
| |
| Packaging content into a Transfer Bundle does not by itself constitute [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_authorization|Transfer Authorization]]. | Creating a Transfer Bundle does not by itself constitute [[dido: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 [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_boundary|Transfer Boundary]]. | Applicable review, approval, inspection, release, transfer, integrity-verification, and import processes govern movement across the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_boundary|Transfer Boundary]]. |
| [[dido: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. | [[dido: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. |
| |
| The Transfer Bundle may contain Artifacts that require separate approval, promotion, validation, or authorization before deployment or operational use. | A Transfer Bundle may contain software packages, but a Transfer Bundle is not itself a software package. |
| |
| ===== Example ===== | ===== Example ===== |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] packages operating-system 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 [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]]. | [[dido: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 [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]]. |
| |
| ---- | ---- |