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

Differences

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

Link to this comparison view

Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-004 [2026/07/18 09:32] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-004 [2026/07/30 05:59] (current) – nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL synchronize an identified [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] between a [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] and a [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] while preserving the Baseline identifier, Revision, composition, provenance, and approval status.+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL synchronize [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] between [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]] and [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]].
  
-===== Source Statement =====+===== Derived From =====
  
-> The system shall support baseline synchronization between connected and disconnected environments.+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-AG-004
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-AG-004.+The Original Requirement states:
  
-===== Assessment =====+> //The system shall support baseline synchronization between connected and disconnected environments.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement identifies the environments and synchronization objective but does not state the information that must remain consistent.+FR-AG-004:
  
-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** 
 +  * Replaces the weak verb **support** with the observable behavior **synchronize** 
 +  * Links **Baselines**, **Connected Environments**, 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 +
-  * **Support** is a weak verb +
-  * **Baseline synchronization** does not identify which Baseline properties must be preserved +
-  * The source statement does not identify whether synchronization is unidirectional or bidirectional +
-  * The source statement does not prescribe a transfer schedule, transport medium, synchronization protocol, repository implementation, or conflict-resolution mechanism +
- +
-The normalized Statement: +
- +
-  * Replaces **The system** with [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] +
-  * Replaces **support** with the direct behavior **synchronize** +
-  * Identifies the Baseline being synchronized +
-  * Uses the defined Connected Environment and Disconnected Environment concepts +
-  * Identifies the Baseline properties that must remain preserved +
-  * Does not assume continuous connectivity +
-  * Preserves implementation independence +
- +
-The normalized Statement does not require bidirectional synchronization. The applicable workflow determines the authorized direction of transfer. +
- +
-**Baseline Synchronization** should receive a glossary definition because it identifies a controlled consistency process rather than simple file copying.+
  
 ===== Rationale ===== ===== Rationale =====
Line 46: Line 30:
 A [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] identifies an approved set of controlled items and relationships. A [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] identifies an approved set of controlled items and relationships.
  
-Synchronization must preserve the identity and meaning of the Baseline across environments.+Baseline synchronization allows an identified Baseline to become available across [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]] and [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] without requiring continuous connectivity between those environments.
  
-Preserved Baseline information includes:+This requirement establishes Baseline synchronization without prescribing:
  
-  * Baseline identifier +  * The direction of synchronization 
-  * Baseline Revision +  * Continuous or bidirectional synchronization 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] +  * The transfer schedule 
-  * Included Artifact identifiers +  * The transport medium 
-  * Included Artifact Revisions +  * The synchronization protocol 
-  * Provenance +  * Conflict-resolution behavior 
-  * Approval status +  * The repository implementation 
-  * Applicable acceptance criteria +  * The properties preserved during synchronization 
-  * Applicable signatures and content digests +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_authorization|Transfer Authorization]] 
-  * Traceability relationships+  * Verification of [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle_integrity|Transfer Bundle Integrity]]
  
-Baseline Synchronization differs from independent Baseline recreation: +Separate requirements, architecture specifications, workflows, or policies define those subjects and behaviors.
- +
-  * Baseline Synchronization transfers and preserves an identified Baseline +
-  * Independent recreation creates another Baseline that may resemble but does not share the same controlled identity +
- +
-Baseline Synchronization does not require both environments to contain every unrelated Baseline.+
  
 ===== Applies To ===== ===== Applies To =====
Line 74: Line 53:
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]]   * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]]
-  * Baseline identifiers 
-  * Baseline Revisions 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Compositions]] 
-  * Baseline approval records 
-  * Baseline provenance 
-  * Baseline traceability 
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]]
   * [[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]]
-  * Artifact Export Packages +  * Baseline synchronization operations
-  * Artifact Import Packages+
  
 ===== Verification ===== ===== Verification =====
  
-  - Verification SHALL confirm that the Baseline selected for synchronization is identified +Verification confirms that:
-  - Verification SHALL confirm that the source and destination environments are identified +
-  - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] synchronizes the identified Baseline between the Connected Environment and the Disconnected Environment +
-  - Verification SHALL confirm that the Baseline identifier remains unchanged +
-  - Verification SHALL confirm that the Baseline Revision remains unchanged +
-  - Verification SHALL confirm that the Baseline Composition remains unchanged +
-  - Verification SHALL confirm that the Baseline provenance and approval status remain preserved+
  
-Verification may include: +  - A [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] is selected for synchronization 
- +  - A [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] and a [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] are selected for testing 
-  * Baseline export and import testing +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] synchronizes the selected Baseline between the tested environments 
-  * Baseline identifier comparison +  - The synchronized Baseline can be identified in the destination environment 
-  * Baseline Revision comparison +  - The result of the tested synchronization operation can be determined
-  * Baseline Composition comparison +
-  * Artifact manifest comparison +
-  * Content-digest comparison +
-  * Provenance comparison +
-  * Approval-record comparison +
- +
-The verification record SHALL identify: +
- +
-  - The synchronized Baseline +
-  - The source environment +
-  - The destination environment +
-  - The Baseline identifier +
-  - The Baseline Revision +
-  - The Baseline Composition +
-  - The Baseline provenance +
-  - The Baseline approval status +
-  - The synchronization result +
-  - 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-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-005|FR-AG-005 — Deployment Traceability Across Disconnected Environments]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start|C.3.9 Baseline Composition and Workspace]] +
-  * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] +
-  * [[dido:02-crusible:08-dependencies-and-air-gap-operations:start|8. Dependencies and Air Gap Operations]]+
  
 ===== Referenced By ===== ===== Referenced By =====
  
-The wiki Backlinks function provides the current list of pages that reference ''FR-AG-004''.+The following pages reference this requirement:
  
-Incoming 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 the controlled transfer of Baselines and their associated Artifacts from Connected Environments to Disconnected Environments.+Implemented and Verified
  
-FR-AG-004 establishes the consistency and identity-preservation requirements for that synchronization.+===== Requirement Status =====
  
-===== Delivery Phase =====+<todo>Review and approve FR-AG-004 as a leaf requirement.</todo>
  
-Phase 1+---- 
 +===== Issues =====
  
-===== Implementation Status =====+<todo>Determine whether Baseline Synchronization requires a controlled definition in the shared Terms and Definitions corpus.</todo>
  
-Not Assessed+<todo>Determine whether separate requirements define the Baseline properties that synchronization must preserve.</todo>
  
-===== Requirement Status ===== +<todo>Determine whether separate requirements define synchronization direction, authorization, scheduling, and conflict handling.</todo>
- +
-Draft+
  
 ---- ----
 ===== Notes for Editors ===== ===== Notes for Editors =====
  
-This requirement page should retain the stable requirement identifier ''FR-AG-004''.+This requirement page retains the stable requirement identifier ''FR-AG-004''.
  
-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 synchronization of an identified Baseline while preserving its controlled identity and composition.+The Statement preserves the approved source intent by requiring Crucible to synchronize Baselines between Connected Environments and Disconnected Environments.
  
-The applicable workflow should define synchronization direction, scheduling, conflict handling, and authorization.+Do not add Baseline identifier, Revision, composition, provenance, approval-status, synchronization-direction, scheduling, authorization, transport, or conflict-resolution obligations unless the controlling requirement changes through an approved requirements process.
  
 To reference this requirement Statement from another wiki page, insert: To reference this requirement Statement from another wiki page, insert:
Line 175: Line 106:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-004#Statement&noheader&nofooter&noeditbtn}} {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-004#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-004.1784392377.txt.gz
  • Last modified: 2026/07/18 09:32
  • by nick_dido