====== C.3.1 Configuration Management ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to Crucible Functional Requirements]]

The [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_management|Configuration Management]] [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|requirements]] define how [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] represents infrastructure through [[dido:99_annexes:annex-b-terms-and-definitions:d:declarative_configuration|Declarative Configuration]], treats [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]] as [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_as_code|Infrastructure as Code]], reuses [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprints]], resolves environment inheritance, and preserves configuration [[dido:99_annexes:annex-b-terms-and-definitions:r:revision_history|Revision History]].

Together, these [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|requirements]] establish controlled and reusable configuration representations that contribute to [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]].

===== Contents =====

{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management#1|js navbar nocookie maxjs#1 id#crucible_configuration_management_requirements_nav}}

===== Notes for Editors =====

The individual [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|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 [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]] [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|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 [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] should use the wiki Backlinks function rather than a manually maintained list.

To reference a requirement Statement from another wiki page, insert:

<code dokuwiki>
{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}
</code>

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.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>