dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-005

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-005 [2026/07/18 09:37] – nick_didodido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-005 [2026/07/30 06:00] (current) – nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL preserve the traceability relationships that connect a [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment]] performed in a [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] to its source [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]], transferred [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], deployment inputs, and deployment results.+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL maintain [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]] [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] across [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]].
  
-===== Source Statement =====+===== Derived From =====
  
-> The system shall maintain [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment]] [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] across [[[[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]].+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-AG-005
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-AG-005.+The Original Requirement states:
  
-===== Assessment =====+> //The system shall maintain deployment traceability across disconnected environments.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement uses a direct verb but does not identify the subjects that must remain traceable.+FR-AG-005:
  
-The following Specification Discipline and Authoring findings apply:+  * Replaces **The system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] 
 +  * Changes **shall** to the established uppercase normative form **SHALL** 
 +  * Links **Deployment**, **Traceability**, and **Disconnected Environments** to their controlling definitions
  
-  * **The system** does not use the defined system name +No other substantive normalization is required.
-  * **shall** does not follow the established uppercase normative convention +
-  * **Maintain** does not identify which traceability relationships must be preserved +
-  * **Across disconnected environments** may imply direct communication even though the environments may not have network connectivity +
-  * The source statement does not identify the source Baseline, transferred Artifacts, deployment inputs, or deployment results +
-  * The source statement does not prescribe a traceability data model, repository, identifier format, transfer mechanism, or implementation technology +
- +
-The normalized Statement: +
- +
-  * Replaces **The system** with [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] +
-  * Replaces the broad verb **maintain** with **preserve** +
-  * Identifies the deployment as the traceability subject +
-  * Identifies the source Baseline +
-  * Identifies the transferred Artifacts +
-  * Identifies the deployment inputs and deployment results +
-  * Does not assume direct network connectivity +
-  * Preserves implementation independence +
- +
-The 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 ===== ===== Rationale =====
  
-Disconnected transfer must not sever the relationships that establish what was built, approved, transferred, imported, and deployed.+[[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]] [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] allows an evaluator to relate a deployment performed within a [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] to the controlled information associated with that deployment.
  
-Deployment traceability may connect:+Relevant traceability information can include relationships among:
  
-  * A deployment identifier 
-  * A source [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Description]] 
-  * A source [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] 
-  * Baseline Revision 
-  * Baseline Composition 
-  * Included Artifact identifiers 
-  * Included Artifact Revisions 
-  * Artifact content digests 
-  * Artifact Export Package identifier 
-  * Transfer Authorization 
-  * Artifact Import Package identifier 
-  * Destination environment 
   * Deployment inputs   * Deployment inputs
-  * Deployment operation +  * Deployment operations 
-  * Deployment result +  * Deployment results 
-  * Deployment Validation result +  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] 
-  * Compliance findings +  * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] 
-  * Generated Evidence+  * Transfer records 
 +  * Validation results 
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  
-Preserving these relationships allows an evaluator to determine whether the deployment performed in a Disconnected Environment corresponds to the approved and transferred source material.+This requirement does not prescribe:
  
-Traceability preservation differs from synchronization:+  * A particular set of traceability relationships 
 +  * A centralized traceability repository 
 +  * Direct network communication among Disconnected Environments 
 +  * A traceability data model 
 +  * An identifier format 
 +  * A transfer mechanism 
 +  * A repository implementation
  
-  * Synchronization preserves the controlled content and identity of a Baseline +Separate requirements, architecture specifications, workflows, or policies define those subjects.
-  * Traceability preservation retains the relationships among the Baseline, transfer records, deployment inputs, and deployment results+
  
 ===== Applies To ===== ===== Applies To =====
Line 78: Line 57:
  
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
-  * Deployments +  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployments]] 
-  * Deployment identifiers +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] +
-  * Baseline Revisions +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Compositions]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] +
-  * Artifact Export Packages +
-  * Artifact Import Packages +
-  * Transfer Authorizations +
-  * Deployment inputs +
-  * Deployment results +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]+
   * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]]   * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]]
  
 ===== Verification ===== ===== Verification =====
  
-  - Verification SHALL confirm that the tested deployment has an identified deployment record +Verification confirms that:
-  - Verification SHALL confirm that the deployment record identifies the source [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] +
-  - Verification SHALL confirm that the deployment record identifies the transferred [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] +
-  - Verification SHALL confirm that the deployment record identifies the deployment inputs +
-  - Verification SHALL confirm that the deployment record identifies the deployment results +
-  - Verification SHALL confirm that the traceability relationships remain available within the Disconnected Environment without access to a Connected Environment+
  
-Verification may include: +  - A Deployment involving one or more Disconnected Environments is selected for testing 
- +  - Traceability information associated with the tested Deployment is identified 
-  * Deployment-record inspection +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] maintains the identified Deployment Traceability across the tested Disconnected Environments 
-  * Baseline traceability inspection +  - The maintained traceability information allows the tested Deployment and its associated controlled information to be related 
-  * Artifact manifest comparison +  - The traceability information remains available without requiring prohibited direct communication between the tested Disconnected Environments
-  * Export-package record inspection +
-  * Import-package record inspection +
-  * Deployment-input comparison +
-  * Deployment-result comparison +
-  * Identifier continuity testing +
-  * Disconnected traceability demonstrations +
- +
-The verification record SHALL identify: +
- +
-  - The deployment identifier +
-  - The Disconnected Environment +
-  - The source Baseline +
-  - The Baseline Revision +
-  - The transferred Artifacts +
-  - The Artifact Export Package +
-  - The Transfer Authorization +
-  - The Artifact Import Package +
-  - The deployment inputs +
-  - The deployment results +
-  - The preserved traceability relationships +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] +
- +
-===== Outgoing Traceability ===== +
- +
-This requirement realizes: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004|MO-004]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006|MO-006]] +
- +
-This requirement relates to: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-001|FR-AG-001 — Disconnected Deployment Operations]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-002|FR-AG-002 — Artifact Export Packages]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-003|FR-AG-003 — Artifact Import Packages]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-004|FR-AG-004 — Baseline Synchronization]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-10-dependency-capture-and-offline-transfer:start|C.3.10 Dependency Capture and Offline Transfer]] +
-  * [[dido:02-crusible:08-dependencies-and-air-gap-operations:start|8. Dependencies and Air Gap Operations]] +
-  * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]]+
  
 ===== Referenced By ===== ===== Referenced By =====
  
-The wiki Backlinks function provides the current list of pages that reference ''FR-AG-005''.+The following pages reference this requirement:
  
-Incoming [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] should be derived dynamically from backlinks rather than maintained as a duplicate manual list.+{{backlinks>.#dido:02-crusible}}
  
-===== ConOps Relationship =====+===== Implementation Status =====
  
-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.+Implemented and Verified
  
-FR-AG-005 preserves those relationships after the deployment enters and operates within a Disconnected Environment.+===== Requirement Status =====
  
-===== Delivery Phase =====+<todo>Review and approve FR-AG-005 as a leaf requirement.</todo>
  
-Phase 1+---- 
 +===== Issues =====
  
-===== Implementation Status ===== +<todo>Determine whether separate requirements define the minimum traceability relationships required for disconnected Deployments.</todo>
- +
-Not Assessed +
- +
-===== Requirement Status =====+
  
-Draft+<todo>Determine whether separate requirements define how traceability information is transferred between environments.</todo>
  
 ---- ----
 ===== Notes for Editors ===== ===== Notes for Editors =====
  
-This requirement page should retain the stable requirement identifier ''FR-AG-005''.+This requirement page retains the stable requirement identifier ''FR-AG-005''.
  
-Changes to the Statement SHALL preserve the approved intent of the source requirement.+This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-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 Statement preserves the approved source intent by requiring Crucible to maintain Deployment Traceability across Disconnected Environments.
  
-The requirement should not imply that Connected and Disconnected Environments maintain direct network communication.+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.
  
-Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations. +Do not interpret **across Disconnected Environments** as requiring direct network communication between those environments.
- +
-Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.+
  
 To reference this requirement Statement from another wiki page, insert: To reference this requirement Statement from another wiki page, insert:
Line 189: Line 110:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-005#Statement&noheader&nofooter&noeditbtn}} {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-005#Statement&noheader&nofooter&noeditbtn}}
 </code> </code>
- 
-Do not rename this page after an external citation unless a redirect or move plan is in place. 
  
 ---- ----
  • dido/02-crusible/99-annexes/annex-c-requirements/03-functional-requirements/03-05-air-gap-operations/fr-ag-005.1784392643.txt.gz
  • Last modified: 2026/07/18 09:37
  • by nick_dido