FR-CFG-005 — Configuration Version History

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

This requirement derives from:

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

The Original Requirement states:

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

FR-CFG-005:

No other substantive normalization is required.

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 comparison
  • Historical configuration retrieval
  • Change review
  • Configuration restoration
  • Configuration audit

This requirement applies to:

Verification confirms that:

  1. A tested Infrastructure Configuration has two or more revisions
  2. Crucible retains each tested revision in the configuration version history
  3. Each tested revision remains distinguishable from the other tested revisions
  4. An authorized user or process can identify and retrieve each tested revision
  5. Creation of a succeeding revision does not overwrite a preceding revision
  6. The version history identifies the order of the tested revisions

The following pages reference this requirement:

Implemented and Verified

Review and approve FR-CFG-005 as a leaf requirement.


Determine whether Configuration Version History requires a controlled definition in the shared Terms and Definitions corpus.

Determine whether separate requirements define revision metadata, retention periods, deletion controls, comparison, or restoration.


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.

  • dido/02-crusible/99-annexes/annex-c-requirements/03-functional-requirements/03-01-configuration-management/fr-cfg-005.txt
  • Last modified: 2026/07/30 05:17
  • by nick_dido