C.3.1 Configuration Management
Go to Crucible Functional Requirements
The Configuration Management requirements define how Crucible represents infrastructure through Declarative Configuration, treats Infrastructure Configuration as Infrastructure as Code, reuses Infrastructure Blueprints, resolves environment inheritance, and preserves configuration Revision History.
Together, these requirements establish controlled and reusable configuration representations that contribute to Reproducibility, Provenance, and Traceability.
Contents
Notes for Editors
The individual requirement pages should retain the stable identifiers FR-CFG-001 through FR-CFG-005.
Individual requirement pages are leaf nodes and should not include a trailing :start in their namespaces.
The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.
Normalized Statements should use direct, testable behavior and should identify the applicable Infrastructure Configuration Artifact, operation, and required result.
Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.
Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.
To reference a requirement Statement from another wiki page, insert:
{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}
Replace <namespace> with the namespace of the requirement leaf page.
The section name following # SHALL match the section heading verbatim on the requirement page.
Do not rename a requirement page after an external citation unless a redirect or move plan is in place.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.