FR-CFG-005 — Configuration Version History

Go to Crucible Configuration Management Requirements

Statement

Crucible SHALL maintain the complete version history of each Infrastructure Configuration.

Derived From

This requirement derives from:

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, Configuration Management, FR-CFG-005The Original Requirement states:

The system SHALL maintain complete configuration version history.[C1]

FR-CFG-005:

Replaces The system with the defined system name CrucibleIdentifies the Infrastructure Configuration as the configuration whose version history is maintainedNo other substantive normalization is required.

Rationale

The version history of an Infrastructure Configuration records the revisions of that configuration over time.

Maintaining the complete version history allows an authorized user or process to identify and retrieve earlier and current configuration revisions.

The version history supports separately governed activities such as:

Revision comparisonHistorical configuration retrievalChange reviewConfiguration restorationConfiguration auditReproducibility

Applies To

This requirement applies to:

Infrastructure Configuration revisionsConfiguration version historyVersion Control

Verification

Verification confirms that:

A tested Infrastructure Configuration has two or more revisionsCrucible retains each tested revision in the configuration version historyEach tested revision remains distinguishable from the other tested revisionsAn authorized user or process can identify and retrieve each tested revisionCreation of a succeeding revision does not overwrite a preceding revisionThe version history identifies the order of the tested revisions

Referenced By

The following pages reference this requirement:

Implementation Status

Implemented and Verified

Requirement Status

Issues

Notes for Editors

This requirement page retains the stable requirement identifier FR-CFG-005.

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 maintain the complete version history of each Infrastructure Configuration.

Do not add approval status, authorship, timestamps, change rationale, retention periods, deletion controls, comparison, restoration, deployment association, provenance, or traceability obligations to the Statement 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-01-configuration-management:fr-cfg-005#Statement&noheader&nofooter&noeditbtn}}

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