Go to 7. Disconnected and Air-Gapped Operations
After successful import of the Transfer Bundle, Crucible uses the imported dependency content to populate repositories available within the destination Disconnected Environment or Air-Gapped Environment.
An Offline Repository provides locally available content that would otherwise require access to an external connected source.
Repository population makes imported Dependencies available to the tools and lifecycle activities that require them. It does not independently authorize use of every imported Dependency.
Crucible identifies the Offline Repositories required by the planned destination lifecycle activity.
The destination environment can contain repositories for:
The applicable dependency type and destination activity determine which repository receives the imported content.
Crucible selects the imported Dependencies intended for each Offline Repository.
The selected content can include:
Crucible preserves the identity of each imported item while preparing it for repository population.
Crucible places the selected imported content into the applicable Offline Repository.
Repository population can include:
The repository representation can differ from the original connected source when the destination tooling requires a different local organization.
A change in repository organization does not change the identity or revision of the preserved Dependency.
Crucible preserves the relationships needed to use the populated repository correctly.
These relationships can identify:
Preserving these relationships supports subsequent construction, assessment, deployment, validation, maintenance, and recovery activities within the destination environment.
Crucible can populate more than one type of Offline Repository when the imported dependency set contains content used by different tools or lifecycle activities.
Repository types can differ in their:
Crucible does not require every Dependency to use one repository format.
The applicable repository implementation determines how the preserved Dependency content becomes available to destination-side tools.
Crucible determines whether the selected imported content became available in the applicable Offline Repository.
Verification can include:
A successful repository-population result establishes that the selected content is available through the Offline Repository. It does not independently establish that the content is compliant, approved, secure, or suitable for every use.
Crucible records conditions that prevent successful repository population.
Exceptions can include:
Crucible does not silently substitute another Dependency version when the selected version cannot be populated.
The applicable operator or workflow determines whether an exception requires correction, replacement of the Transfer Bundle, additional import activity, or another authorized response.
The repository-population result identifies:
The populated Offline Repositories provide controlled inputs to 7.6 Rebuild and Deploy.
| Requirement | Statement |
|---|---|
| FR-DEPC-004 — Populate Offline Repositories |
Crucible SHALL populate Offline Repositories in a Disconnected Environment from a Transfer Bundle. |
The linked leaf requirement page remains the canonical source.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.