FR-CFG-005 — Configuration Version History

Go to Crucible Configuration Management Requirements

Statement

Crucible SHALL preserve each revision of an Infrastructure Configuration and the relationship between successive revisions.

Source Statement

The system SHALL maintain complete configuration version history.

Source

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, Configuration Management, FR-CFG-005.

Assessment

The source statement expresses the approved functional intent but does not provide all information required for deterministic verification.

The following Specification, Discipline and Authoring findings apply:

The system does not use the defined system nameMaintain does not identify the specific behavior Crucible performsConfiguration does not identify the configuration artifact to which the requirement appliesComplete does not identify the minimum content required for completenessVersion history does not identify whether the history includes revision content, revision identifiers, revision relationships, or other revision metadataThe source statement does not identify the observable result used to verify preservation of the version historyThe normalized Statement:

Replaces The system with the defined system nameReplaces maintain with the direct behavior preserveIdentifies the Infrastructure Configuration as the controlled artifactRequires preservation of every Infrastructure Configuration revisionRequires preservation of the relationship between successive revisionsThe normalized Statement interprets complete configuration version history as the preserved set of Infrastructure Configuration revisions and the succession relationships that order those revisions.

The normalized Statement does not introduce approval, authorship, timestamp, change-rationale, retention-period, rollback, deployment, provenance, or traceability obligations. Separate requirements govern those behaviors when required.

Rationale

Configuration version history records how an Infrastructure Configuration changes over time.

Each revision represents a distinguishable state of the Infrastructure Configuration.

Preserving the relationship between successive revisions establishes the order in which those states occurred.

Without preserved revisions and succession relationships, an organization cannot reliably determine:

Which configuration states existedHow one configuration state followed anotherWhether a later revision replaced an earlier revisionWhich revision represents a particular historical configuration stateConfiguration version history provides a foundation for separately governed activities such as:

Revision comparisonPrior-state reconstructionChange reviewRollbackConfiguration drift analysisAuditReproducibilityThis requirement complements FR-CFG-002:

FR-CFG-002 requires each Infrastructure Configuration to exist as a machine-readable Artifact managed through Version ControlFR-CFG-005 requires preservation of every configuration revision and the relationships among successive revisions

Applies To

This requirement applies to:

Infrastructure Configuration revisionsRevision contentSuccessive revision relationshipsConfiguration version historyVersion ControlVersion Control Systems

Verification

Verification SHALL confirm that each tested Infrastructure Configuration revision remains preserved after a succeeding revision is createdVerification SHALL confirm that the content of each tested revision remains distinguishable from the content of every other tested revisionVerification SHALL confirm that each tested revision identifies the immediately preceding revision when a preceding revision existsVerification SHALL confirm that the preserved succession relationships place the tested revisions in their correct revision orderVerification SHALL confirm that creation of a succeeding revision does not overwrite the content of a preceding revisionVerification may include:

Configuration revision inspectionRevision content comparisonSuccessive revision testsRevision relationship inspectionRevision-order reconstructionRevision overwrite testsVersion Control System history inspectionThe verification record SHALL identify:

The tested Infrastructure ConfigurationThe tested revisionsThe content associated with each tested revisionThe preceding revision associated with each tested revision, when applicableThe reconstructed revision orderThe revision overwrite test resultThe observed resultsThe generated Evidence

Outgoing Traceability

This requirement refines:

This requirement operates within the conditions established by:

This requirement also relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference FR-CFG-005.

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

Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship.

ConOps Relationship

The Crucible Concept of Operations describes the use of version-controlled configuration inputs within a CI/CD Pipeline workspace.

Preserved configuration revisions allow the workflow to:

Identify a particular Infrastructure Configuration stateDistinguish that state from earlier and later revisionsDetermine the preceding revisionReconstruct the order of configuration revisionsUse an identified historical configuration state in a separately governed activityThe preserved revision history provides the sequence of Infrastructure Configuration states used to understand how the configuration changed over time.

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification that Crucible preserves each Infrastructure Configuration revision and the relationship between successive revisions.

Requirement Status

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.

Notes for Editors

This requirement page should retain the stable requirement identifier FR-CFG-005.

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

Material changes should receive review and should update the related outbound traceability, verification criteria, and source records.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

Verification criteria should test only the preservation of Infrastructure Configuration revisions and their successive relationships.

Approval status, authorship, timestamps, change rationale, retention periods, deletion controls, comparison, rollback, deployment association, provenance, and traceability should not be introduced as normative behavior on this page unless the Statement changes through an approved requirements process.

Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:fr-cfg-005#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.