FR-AG-001 — Disconnected Deployment Operations

Go to Crucible Air-Gapped Operations Requirements

Statement

Crucible SHALL execute an identified Deployment Operation within a Disconnected Environment without direct electronic communication with specified external systems, services, repositories, Providers, or networks.

Source Statement

The system shall support disconnected deployment operations.

Source

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-AG-001.

Assessment

The source statement identifies the intended operating condition but does not provide a fully testable formulation.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system nameshall does not follow the established uppercase normative conventionSupport is a weak verb that does not identify the required behaviorDisconnected deployment operations does not use the defined Deployment Operation conceptDisconnected deployment operations does not use the defined Disconnected Environment conceptThe source statement does not identify the communication restrictions that govern executionThe source statement does not identify the external subjects with which communication is prohibitedThe source statement does not prescribe a deployment tool, transfer mechanism, repository implementation, network technology, Provider, or target platformThe normalized Statement:

Replaces The system with CrucibleReplaces support with the direct behavior executeUses the defined Deployment Operation conceptUses the defined Disconnected Environment conceptRequires identification of the Deployment OperationIdentifies the external communication restrictions that govern executionPreserves implementation independenceRetains one primary required behaviorThe normalized Statement does not require every Dependency to originate within the Disconnected Environment.

Separate requirements govern:

Controlled transferArtifact exportArtifact importTransfer AuthorizationTransfer Bundle IntegrityBaseline synchronization

Rationale

A Disconnected Environment operates without direct electronic communication with specified external systems, services, repositories, Providers, or networks.

The Disconnected Environment therefore relies on locally available:

SoftwareDependenciesRepositoriesServicesConfiguration informationCredentialsOperational dataArtifactsValidation resourcesControlled transfer processes supply new or updated material when the Disconnected Environment cannot communicate directly with the original source.

Before Crucible executes a Deployment Operation, the Disconnected Environment must contain or have authorized local access to the Artifacts, configurations, Dependencies, credentials, metadata, and other resources required by that Deployment Operation.

A Deployment Operation may create, configure, update, replace, or remove:

ConfigurationRelationships among deployed subjectsA Deployment Operation may use:

A Crucible DescriptionAn Infrastructure ConfigurationAn Infrastructure BaselineA Machine ImageA Container ImagePlatform Independent InformationPlatform Specific InformationRelated deployment activities may include:

A Disconnected Environment may retain internal network connectivity among its components. The communication restriction applies to the specified external systems, services, repositories, Providers, or networks identified by the applicable operational boundary.

A Disconnected Environment differs from an Air-Gapped Environment:

A Disconnected Environment operates without direct electronic communication with specified external subjectsAn Air-Gapped Environment is separated from external subjects by an intentionally maintained Air GapAn Air-Gapped Environment is a specialized Disconnected Environment.

Applies To

This requirement applies to:

Deployment subjectsArtifactsDependenciesLocal repositoriesLocal configuration sourcesLocal credentialsLocal validation resourcesInfrastructure ResourcesVirtual MachinesKubernetes ClustersContainerized WorkloadsPlatform ServicesCI/CD Pipelines

Verification

Verification SHALL confirm that the tested environment satisfies the definition of a Disconnected EnvironmentVerification SHALL identify the Deployment Operation selected for testingVerification SHALL identify the external systems, services, repositories, Providers, or networks with which direct electronic communication is prohibitedVerification SHALL confirm that Crucible executes the identified Deployment Operation within the Disconnected EnvironmentVerification SHALL confirm that Crucible does not establish direct electronic communication with the specified external systems, services, repositories, Providers, or networks during the Deployment OperationVerification SHALL confirm that the Deployment Operation produces the expected deployment resultVerification may include:

Disconnected deployment testingNetwork boundary inspectionExternal communication monitoringLocal repository inspectionDependency availability inspectionDeployment output inspectionDeployment log inspectionDeployment ValidationThe verification record SHALL identify:

The Disconnected EnvironmentThe tested Deployment OperationThe deployment subjectsThe locally available ArtifactsThe locally available DependenciesThe specified external systems, services, repositories, Providers, or networksThe observed electronic communicationThe deployment resultThe generated Evidence

Outgoing Traceability

This requirement realizes:

This requirement relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference FR-AG-001.

Incoming Traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship.

ConOps Relationship

The Crucible Concept of Operations describes a connected-to-disconnected supply chain in which Dependencies and Artifacts are captured in a Connected Environment, transferred across an authorized Transfer Boundary, and consumed within a Disconnected Environment.

FR-AG-001 establishes the required behavior for executing a Deployment Operation after the required Artifacts and Dependencies enter the Disconnected Environment.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Implementation status requires verification that Crucible executes an identified Deployment Operation within a Disconnected Environment without direct electronic communication with specified external systems, services, repositories, Providers, or networks.

Requirement Status

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.

Notes for Editors

This requirement page should retain the stable requirement identifier FR-AG-001.

Changes to the Statement SHALL preserve the approved intent of the source requirement.

The Source Statement should preserve the original visible wording from the controlling System Requirements Specification while linking applicable words and phrases to the controlling Terms and Definitions entries.

The Statement should remain limited to execution of an identified Deployment Operation within a Disconnected Environment without direct electronic communication with specified external systems, services, repositories, Providers, or networks.

Requirements for Artifact export, Artifact import, Dependency Capture, synchronization, Transfer Authorization, and Transfer Bundle Integrity should remain in their applicable requirement pages.

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 this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-001#Statement&noheader&nofooter&noeditbtn}}

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

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