Crucible SHALL maintain Deployment Traceability across Disconnected Environments.
This requirement derives from:
The Original Requirement states:
The system shall maintain deployment traceability across disconnected environments.[C1]
FR-AG-005:
No other substantive normalization is required.
Deployment Traceability allows an evaluator to relate a deployment performed within a Disconnected Environment to the controlled information associated with that deployment.
Relevant traceability information can include relationships among:
This requirement does not prescribe:
Separate requirements, architecture specifications, workflows, or policies define those subjects.
This requirement applies to:
Verification confirms that:
The following pages reference this requirement:
Implemented and Verified
Review and approve FR-AG-005 as a leaf requirement.
Determine whether separate requirements define the minimum traceability relationships required for disconnected Deployments.
Determine whether separate requirements define how traceability information is transferred between environments.
This requirement page retains the stable requirement identifier FR-AG-005.
This page is a leaf requirement page and omits a trailing :start from its namespace.
The Statement preserves the approved source intent by requiring Crucible to maintain Deployment Traceability across Disconnected Environments.
Do not add a mandatory list of source Baselines, transferred Artifacts, deployment inputs, deployment results, transfer records, or Evidence to the Statement unless the controlling requirement changes through an approved requirements process.
Do not interpret across Disconnected Environments as requiring direct network communication between those environments.
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}}
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.