FR-CFG-005 — Configuration Version History

Go to Crucible Configuration Management Requirements

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

The system SHALL maintain complete configuration version history.

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

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 name
• Maintain does not identify the specific preservation behavior that Crucible performs
• Configuration does not identify the configuration artifact to which the requirement applies
• Complete does not identify the records required for completeness
• Version history does not identify whether the requirement applies to revision content, revision identifiers, revision relationships, authorship, timestamps, approval status, or change rationale
• The source statement does not identify whether a prior revision must remain retrievable
• The source statement does not identify whether a revision may be deleted or altered
• The source statement does not define the retention period for configuration history
• The source statement does not identify the records required to preserve Provenance, Auditability, and Traceability

The 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.

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 configuration
• Compare two revisions
• Determine when a change occurred
• Identify the source of a configuration change
• Associate a deployed environment with the configuration revision used
• Investigate configuration drift
• Restore a prior valid configuration
• Demonstrate Auditability
• Preserve Traceability

Crucible 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 comparison
• Change review
• Change approval
• Prior revision retrieval
• Rollback
• Configuration drift analysis
• Environment reconstruction
• Compliance review

Configuration version history supports:

• Reproducibility
• Provenance
• Auditability
• Traceability

This requirement applies to:

• Crucible
• Infrastructure Configurations
• Declarative Configuration
• Infrastructure Blueprints
• Parent Infrastructure Configurations
• Child Infrastructure Configurations
• Resolved configurations
• Revisions
• Revision History
• Revision content
• Revision relationships
• Version Control
• Configuration Management
• Provenance
• Auditability
• Reproducibility
• Traceability

1. Verification SHALL confirm that each tested Infrastructure Configuration revision remains preserved after a succeeding revision is created
2. Verification SHALL confirm that the preserved content of each tested revision remains distinguishable from the content of other revisions
3. Verification SHALL confirm that each tested revision identifies its preceding revision when a preceding revision exists
4. Verification SHALL confirm that each tested revision identifies its succeeding revision when a succeeding revision exists
5. Verification SHALL confirm that an authorized user can retrieve each tested revision
6. Verification SHALL confirm that retrieval of a prior revision does not alter the preserved revision content
7. Verification SHALL confirm that a newly created revision does not overwrite the preserved content of a prior revision
8. Verification SHALL confirm that the revision history preserves the applicable Provenance and Traceability

Verification may include:

• Revision history inspection
• Revision content inspection
• Revision relationship inspection
• Successive revision tests
• Prior revision retrieval tests
• Prior revision integrity tests
• Revision overwrite tests
• Repository history inspection
• Provenance record inspection
• Traceability record inspection

The verification record SHALL identify:

1. The tested Infrastructure Configuration
2. The tested revisions
3. The preserved content associated with each revision
4. The preceding revision relationships
5. The succeeding revision relationships
6. The revision retrieval results
7. The revision integrity results
8. The applicable Provenance
9. The observed results
10. The generated Evidence

This requirement refines:

• MO-001 — Repeatable, Compliant, and Secure Infrastructure Environments
• MO-005 — Reusable and Version-Controlled Infrastructure
• MO-006 — Infrastructure Lifecycle Management

This requirement operates within the conditions established by:

• OR-001 — Operational Roles
• OR-002 — Deployment Environments
• OR-003 — Classified and Unclassified Environments
• OR-004 — Concurrent Environment Management
• OR-005 — Distributed Environment Management

This requirement also relates to:

• 5. Descriptions, Composition, and Baselines
• 7. Infrastructure and Deployment
• 10. Reproducibility, Provenance, and Traceability

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.

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 revision
• Compare configuration revisions
• Select an approved revision
• Associate a configuration revision with an execution
• Reconstruct a prior configuration state
• Investigate configuration drift
• Preserve execution history
• Preserve Provenance and Traceability

The preserved revision history provides the configuration record required to reproduce, review, and audit infrastructure changes over time.

Phase 1 and subsequent phases

Not Assessed

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

Draft

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

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.