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 preservation behavior that Crucible performsConfiguration does not identify the configuration artifact to which the requirement appliesComplete does not identify the records required for completenessVersion history does not identify whether the requirement applies to revision content, revision identifiers, revision relationships, authorship, timestamps, approval status, or change rationaleThe source statement does not identify whether a prior revision must remain retrievableThe source statement does not identify whether a revision may be deleted or alteredThe source statement does not define the retention period for configuration historyThe source statement does not identify the records required to preserve Provenance, Auditability, and TraceabilityThe normalized Statement replaces the broad verb with preserve, identifies the Infrastructure Configuration as the controlled artifact, and requires preservation of each revision and the relationships among successive revisions.

Revision identification, authorship, timestamps, change rationale, approval status, deletion controls, and retention periods require evaluation during the Configuration Management completeness review before allocation to this requirement or creation of derived requirements.

Rationale

Configuration history allows an organization to determine how an Infrastructure Configuration changes over time.

Without preserved revision content and revision relationships, an organization cannot reliably:

Reconstruct a prior configurationCompare two revisionsDetermine when a change occurredIdentify the source of a configuration changeAssociate a deployed environment with the configuration revision usedInvestigate configuration driftRestore a prior valid configurationDemonstrate AuditabilityPreserve TraceabilityCrucible preserves each configuration revision as a distinct historical state.

The preserved revision relationship identifies the preceding revision and, when applicable, the succeeding revision.

This history provides the foundation for separately defined behaviors such as:

Revision comparisonChange reviewChange approvalPrior revision retrievalRollbackConfiguration drift analysisEnvironment reconstructionCompliance reviewConfiguration version history supports:

Applies To

This requirement applies to:

Parent Infrastructure ConfigurationsChild Infrastructure ConfigurationsResolved configurationsRevisionsRevision HistoryRevision contentRevision relationshipsVersion ControlConfiguration ManagementProvenanceAuditabilityReproducibilityTraceability

Verification

Verification SHALL confirm that each tested Infrastructure Configuration revision remains preserved after a succeeding revision is createdVerification SHALL confirm that the preserved content of each tested revision remains distinguishable from the content of other revisionsVerification SHALL confirm that each tested revision identifies its preceding revision when a preceding revision existsVerification SHALL confirm that each tested revision identifies its succeeding revision when a succeeding revision existsVerification SHALL confirm that an authorized user can retrieve each tested revisionVerification SHALL confirm that retrieval of a prior revision does not alter the preserved revision contentVerification SHALL confirm that a newly created revision does not overwrite the preserved content of a prior revisionVerification SHALL confirm that the revision history preserves the applicable Provenance and TraceabilityVerification may include:

Revision history inspectionRevision content inspectionRevision relationship inspectionSuccessive revision testsPrior revision retrieval testsPrior revision integrity testsRevision overwrite testsRepository history inspectionProvenance record inspectionTraceability record inspectionThe verification record SHALL identify:

The tested Infrastructure ConfigurationThe tested revisionsThe preserved content associated with each revisionThe preceding revision relationshipsThe succeeding revision relationshipsThe revision retrieval resultsThe revision integrity resultsThe applicable ProvenanceThe 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.

The Phase 1 workflow uses preserved configuration history to:

Retrieve an identified configuration revisionCompare configuration revisionsSelect an approved revisionAssociate a configuration revision with an executionReconstruct a prior configuration stateInvestigate configuration driftPreserve execution historyPreserve Provenance and TraceabilityThe preserved revision history provides the configuration record required to reproduce, review, and audit infrastructure changes 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 relationships among 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, revision records, and source records.

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

The Configuration Management completeness review should evaluate whether unique revision identifiers, authorship, timestamps, change rationale, approval status, deletion controls, retention periods, comparison, rollback, and environment-to-revision traceability require derived requirements.

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.