FR-AG-004 — Baseline Synchronization

Go to Crucible Air-Gapped Operations Requirements

Crucible SHALL synchronize an identified Baseline between a Connected Environment and a Disconnected Environment while preserving the Baseline identifier, Revision, composition, provenance, and approval status.

The system shall support baseline synchronization between connected and disconnected environments.

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

The source statement identifies the environments and synchronization objective but does not state the information that must remain consistent.

The following Specification Discipline and Authoring findings apply:

• The system does not use the defined system name
• 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 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.

A Baseline identifies an approved set of controlled items and relationships.

Synchronization must preserve the identity and meaning of the Baseline across environments.

Preserved Baseline information includes:

• Baseline identifier
• Baseline Revision
• Baseline Composition
• Included Artifact identifiers
• Included Artifact Revisions
• Provenance
• Approval status
• Applicable acceptance criteria
• Applicable signatures and content digests
• Traceability relationships

Baseline Synchronization differs from independent Baseline recreation:

• 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.

This requirement applies to:

• Crucible
• Baselines
• Baseline identifiers
• Baseline Revisions
• Baseline Compositions
• Baseline approval records
• Baseline provenance
• Baseline traceability
• Connected Environments
• Disconnected Environments
• Artifact Export Packages
• Artifact Import Packages

1. Verification SHALL confirm that the Baseline selected for synchronization is identified
2. Verification SHALL confirm that the source and destination environments are identified
3. Verification SHALL confirm that Crucible synchronizes the identified Baseline between the Connected Environment and the Disconnected Environment
4. Verification SHALL confirm that the Baseline identifier remains unchanged
5. Verification SHALL confirm that the Baseline Revision remains unchanged
6. Verification SHALL confirm that the Baseline Composition remains unchanged
7. Verification SHALL confirm that the Baseline provenance and approval status remain preserved

Verification may include:

• Baseline export and import testing
• Baseline identifier comparison
• Baseline Revision comparison
• Baseline Composition comparison
• Artifact manifest comparison
• Content-digest comparison
• Provenance comparison
• Approval-record comparison

The verification record SHALL identify:

1. The synchronized Baseline
2. The source environment
3. The destination environment
4. The Baseline identifier
5. The Baseline Revision
6. The Baseline Composition
7. The Baseline provenance
8. The Baseline approval status
9. The synchronization result
10. The generated Evidence

This requirement realizes:

• MO-004
• MO-006

This requirement relates to:

• FR-AG-002 — Artifact Export Packages
• FR-AG-003 — Artifact Import Packages
• FR-AG-005 — Deployment Traceability Across Disconnected Environments
• C.3.9 Baseline Composition and Workspace
• 5. Descriptions, Composition, and Baselines
• 8. Dependencies and Air Gap Operations

The wiki Backlinks function provides the current list of pages that reference FR-AG-004.

Incoming Traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

The Crucible Concept of Operations describes the controlled transfer of Baselines and their associated Artifacts from Connected Environments to Disconnected Environments.

FR-AG-004 establishes the consistency and identity-preservation requirements for that synchronization.

Phase 1

Not Assessed

Draft

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

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

The Statement should remain limited to synchronization of an identified Baseline while preserving its controlled identity and composition.

The applicable workflow should define synchronization direction, scheduling, conflict handling, and authorization.

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-004#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.