FR-AG-004 — Baseline Synchronization
Statement
Crucible SHALL synchronize Baselines between Connected Environments and Disconnected Environments.
Derived From
This requirement derives from:
-
Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-AG-004
The Original Requirement states:
The system shall support baseline synchronization between connected and disconnected environments.[C1]
FR-AG-004:
-
Replaces The system with the defined system name 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
No other substantive normalization is required.
Rationale
A Baseline identifies an approved set of controlled items and relationships.
Baseline synchronization allows an identified Baseline to become available across Connected Environments and Disconnected Environments without requiring continuous connectivity between those environments.
This requirement establishes Baseline synchronization without prescribing:
-
The direction of synchronization
-
Continuous or bidirectional synchronization
-
The transfer schedule
-
The transport medium
-
The synchronization protocol
-
Conflict-resolution behavior
-
The repository implementation
-
The properties preserved during synchronization
-
Verification of Transfer Bundle Integrity
Separate requirements, architecture specifications, workflows, or policies define those subjects and behaviors.
Applies To
This requirement applies to:
-
Baseline synchronization operations
Verification
Verification confirms that:
-
A Baseline is selected for synchronization
-
A Connected Environment and a Disconnected Environment are selected for testing
-
Crucible synchronizes the selected Baseline between the tested environments
-
The synchronized Baseline can be identified in the destination environment
-
The result of the tested synchronization operation can be determined
Referenced By
The following pages reference this requirement:
Implementation Status
Implemented and Verified
Requirement Status
Review and approve FR-AG-004 as a leaf requirement.
Issues
Determine whether Baseline Synchronization requires a controlled definition in the shared Terms and Definitions corpus.
Determine whether separate requirements define the Baseline properties that synchronization must preserve.
Determine whether separate requirements define synchronization direction, authorization, scheduling, and conflict handling.
Notes for Editors
This requirement page retains the stable requirement identifier FR-AG-004.
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 synchronize Baselines between Connected Environments and Disconnected Environments.
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:
{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-004#Statement&noheader&nofooter&noeditbtn}}
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.