FR-AG-001 — Disconnected Deployment Operations

Go to Crucible Air-Gapped Operations Requirements

Statement

Crucible SHALL perform deployment operations within a Disconnected Environment without accessing an external network resource.

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 identify the environmental condition that governs executionThe source statement does not identify whether external network resources may be accessedThe source statement does not prescribe a deployment tool, transfer mechanism, repository implementation, network technology, or target platformThe normalized Statement:

Replaces The system with CrucibleReplaces support with the direct behavior performIdentifies deployment operations as the required activityUses the defined Disconnected Environment conceptExcludes access to external network resources during the deployment operationPreserves implementation independenceRetains one primary required behaviorThe normalized Statement does not require every dependency to originate within the Disconnected Environment. Separate requirements govern dependency capture, transfer, import, authorization, integrity verification, and synchronization.

Rationale

A Disconnected Environment cannot depend on continuous access to external repositories, services, interfaces, or management systems.

Before deployment begins, the environment must contain or have authorized access to the artifacts, configurations, dependencies, credentials, metadata, and other resources required by the deployment.

Disconnected deployment operations may include:

Deployment of Infrastructure ResourcesDeployment of Virtual MachinesDeployment of Kubernetes ClustersDeployment of Containerized WorkloadsDeployment of Platform ServicesDeployment ValidationDeployment RollbackA Disconnected Environment differs from an Air-Gapped Environment because a Disconnected Environment may lack current connectivity without necessarily implementing the controlled physical or logical isolation associated with an Air-Gapped Environment.

Applies To

This requirement applies to:

Deployment operationsDeployment subjectsImported artifactsImported dependenciesLocal repositoriesLocal configuration sourcesLocal credentialsLocal validation resourcesCI/CD Pipelines

Verification

Verification SHALL confirm that the tested deployment occurs within a Disconnected EnvironmentVerification SHALL confirm that Crucible performs the identified deployment operationVerification SHALL confirm that Crucible does not access an external network resource during the deployment operationVerification SHALL confirm that the deployment produces the expected deployment resultVerification may include:

Network isolation testingExternal resource access monitoringDisconnected deployment testingLocal repository inspectionDependency availability inspectionDeployment output inspectionDeployment log inspectionThe verification record SHALL identify:

The Disconnected EnvironmentThe deployment operationThe deployment subjectsThe locally available artifacts and dependenciesThe prohibited external network resourcesThe observed network activityThe 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.

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 through an authorized boundary, and consumed within a Disconnected Environment.

FR-AG-001 establishes the required deployment behavior after the required resources enter the Disconnected Environment.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Implementation status requires verification that Crucible performs deployment operations in a Disconnected Environment without accessing any external network resources.

Requirement Status

Draft

Notes for Editors

This requirements 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 wording from the controlling System Requirements Specification.

The Statement should remain limited to the performance of deployment operations within a Disconnected Environment without access to external network resources.

Requirements for artifact export, artifact import, dependency capture, synchronization, and transfer authorization 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.