FR-AG-004 — Baseline Synchronization

Go to Crucible Air-Gapped Operations Requirements

Statement

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.

Source Statement

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

Source

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

Assessment

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 nameshall does not follow the established uppercase normative conventionSupport is a weak verbBaseline synchronization does not identify which Baseline properties must be preservedThe source statement does not identify whether synchronization is unidirectional or bidirectionalThe source statement does not prescribe a transfer schedule, transport medium, synchronization protocol, repository implementation, or conflict-resolution mechanismThe normalized Statement:

Replaces The system with CrucibleReplaces support with the direct behavior synchronizeIdentifies the Baseline being synchronizedUses the defined Connected Environment and Disconnected Environment conceptsIdentifies the Baseline properties that must remain preservedDoes not assume continuous connectivityPreserves implementation independenceThe 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

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 identifierBaseline RevisionBaseline CompositionIncluded Artifact identifiersIncluded Artifact RevisionsProvenanceApproval statusApplicable acceptance criteriaApplicable signatures and content digestsTraceability relationshipsBaseline Synchronization differs from independent Baseline recreation:

Baseline Synchronization transfers and preserves an identified BaselineIndependent recreation creates another Baseline that may resemble but does not share the same controlled identityBaseline Synchronization does not require both environments to contain every unrelated Baseline.

Applies To

This requirement applies to:

Baseline identifiersBaseline RevisionsBaseline CompositionsBaseline approval recordsBaseline provenanceBaseline traceabilityConnected EnvironmentsDisconnected EnvironmentsArtifact Export PackagesArtifact Import Packages

Verification

Verification SHALL confirm that the Baseline selected for synchronization is identifiedVerification SHALL confirm that the source and destination environments are identifiedVerification SHALL confirm that Crucible synchronizes the identified Baseline between the Connected Environment and the Disconnected EnvironmentVerification SHALL confirm that the Baseline identifier remains unchangedVerification SHALL confirm that the Baseline Revision remains unchangedVerification SHALL confirm that the Baseline Composition remains unchangedVerification SHALL confirm that the Baseline provenance and approval status remain preservedVerification may include:

Baseline export and import testingBaseline identifier comparisonBaseline Revision comparisonBaseline Composition comparisonArtifact manifest comparisonContent-digest comparisonProvenance comparisonApproval-record comparisonThe verification record SHALL identify:

The synchronized BaselineThe source environmentThe destination environmentThe Baseline identifierThe Baseline RevisionThe Baseline CompositionThe Baseline provenanceThe Baseline approval statusThe synchronization resultThe 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-004.

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

ConOps Relationship

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.

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

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.