C.3.5 Air-Gapped Operations

Go to Crucible Functional Requirements

The Air-Gapped Operations requirements define how Crucible performs deployment operations within Disconnected Environments and Air-Gapped Environments, exports and imports controlled Artifact packages, synchronizes Baselines, and preserves deployment Traceability across disconnected environments.

Together, these requirements establish controlled disconnected operation and Offline Transfer behavior across Transfer Boundaries while preserving applicable Transfer Authorization, Transfer Bundle Integrity, Provenance, and Traceability.

Contents

Notes for Editors

The individual requirement pages should retain the stable identifiers FR-AG-001 through FR-AG-005.

Individual requirement pages are leaf nodes and should not include a trailing :start in their namespaces.

The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.

Normalized Statements should use direct, testable behavior and should identify the applicable source environment, destination environment, transfer subject, Transfer Boundary, operation, and required result.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.

To reference a requirement Statement from another wiki page, insert:

{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}

Replace <namespace> with the namespace of the requirement leaf page.

The section name following # SHALL match the section heading verbatim on the requirement page.

Do not rename a requirement page after an external citation unless a redirect or move plan is in place.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.