FR-AG-005 — Deployment Traceability Across Disconnected Environments

Go to Crucible Air-Gapped Operations Requirements

Statement

Crucible SHALL preserve the traceability relationships that connect a Deployment performed in a Disconnected Environment to its source Baseline, transferred Artifacts, deployment inputs, and deployment results.

Source Statement

The system shall maintain Deployment traceability across Disconnected Environments.

Source

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

Assessment

The source statement uses a direct verb but does not identify the subjects that must remain traceable.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system nameshall does not follow the established uppercase normative conventionMaintain does not identify which traceability relationships must be preservedAcross disconnected environments may imply direct communication even though the environments may not have network connectivityThe source statement does not identify the source Baseline, transferred Artifacts, deployment inputs, or deployment resultsThe source statement does not prescribe a traceability data model, repository, identifier format, transfer mechanism, or implementation technologyThe normalized Statement:

Replaces The system with CrucibleReplaces the broad verb maintain with preserveIdentifies the deployment as the traceability subjectIdentifies the source BaselineIdentifies the transferred ArtifactsIdentifies the deployment inputs and deployment resultsDoes not assume direct network connectivityPreserves implementation independenceThe normalized Statement does not require a centralized traceability repository. Traceability records may travel with exported and imported packages and may be retained independently within each environment.

Rationale

Disconnected transfer must not sever the relationships that establish what was built, approved, transferred, imported, and deployed.

Deployment traceability may connect:

A deployment identifierA source Crucible DescriptionA source BaselineBaseline RevisionBaseline CompositionIncluded Artifact identifiersIncluded Artifact RevisionsArtifact content digestsArtifact Export Package identifierTransfer AuthorizationArtifact Import Package identifierDestination environmentDeployment inputsDeployment operationDeployment resultDeployment Validation resultCompliance findingsGenerated EvidencePreserving these relationships allows an evaluator to determine whether the deployment performed in a Disconnected Environment corresponds to the approved and transferred source material.

Traceability preservation differs from synchronization:

Synchronization preserves the controlled content and identity of a BaselineTraceability preservation retains the relationships among the Baseline, transfer records, deployment inputs, and deployment results

Applies To

This requirement applies to:

DeploymentsDeployment identifiersBaselinesBaseline RevisionsBaseline CompositionsArtifactsArtifact Export PackagesArtifact Import PackagesTransfer AuthorizationsDeployment inputsDeployment resultsEvidenceDisconnected Environments

Verification

Verification SHALL confirm that the tested deployment has an identified deployment recordVerification SHALL confirm that the deployment record identifies the source BaselineVerification SHALL confirm that the deployment record identifies the transferred ArtifactsVerification SHALL confirm that the deployment record identifies the deployment inputsVerification SHALL confirm that the deployment record identifies the deployment resultsVerification SHALL confirm that the traceability relationships remain available within the Disconnected Environment without access to a Connected EnvironmentVerification may include:

Deployment-record inspectionBaseline traceability inspectionArtifact manifest comparisonExport-package record inspectionImport-package record inspectionDeployment-input comparisonDeployment-result comparisonIdentifier continuity testingDisconnected traceability demonstrationsThe verification record SHALL identify:

The deployment identifierThe Disconnected EnvironmentThe source BaselineThe Baseline RevisionThe transferred ArtifactsThe Artifact Export PackageThe Transfer AuthorizationThe Artifact Import PackageThe deployment inputsThe deployment resultsThe preserved traceability relationshipsThe 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-005.

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 build, compliance, dependency, transfer, import, and deployment records remain associated with the Artifacts they describe.

FR-AG-005 preserves those relationships after the deployment enters and operates within a Disconnected Environment.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Requirement Status

Draft

Notes for Editors

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

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

The Statement should remain limited to preservation of traceability relationships connecting a disconnected deployment to its source Baseline, transferred Artifacts, deployment inputs, and deployment results.

The requirement should not imply that Connected and Disconnected Environments maintain direct network communication.

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-005#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.