FR-CFG-002 — Infrastructure as Code

Go to Crucible Configuration Management Requirements

Statement

Crucible SHALL represent each Infrastructure Configuration as a machine-readable, version-controlled Artifact.

Source Statement

The system SHALL support Infrastructure-as-Code methodologies.

Source

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

Assessment

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 nameSupport is a weak verb that does not identify the behavior Crucible performsInfrastructure-as-Code does not identify the infrastructure information represented as codeMethodologies does not identify the required representation, controls, records, or outcomesThe source statement does not identify whether the infrastructure representation must be machine-readableThe source statement does not identify whether the representation must be maintained through Version ControlThe source statement does not distinguish the representation of infrastructure configuration from the separate behaviors used to validate, compare, review, approve, authorize, apply, or retire that configurationThe source statement does not identify the records required to preserve Provenance, Auditability, and TraceabilityThe normalized Statement replaces the weak verb with represent, identifies the Infrastructure Configuration as the controlled Artifact, and defines machine readability and Version Control as required characteristics of the representation.

The source statement does not identify validation, comparison, review, approval, authorization, application, rollback, or retirement behavior. These candidate obligations require evaluation against FR-CFG-003 through FR-CFG-005 before allocation to this requirement or creation of derived requirements.

Rationale

Infrastructure as Code applies software configuration management disciplines to infrastructure definitions.

An Infrastructure Configuration that exists only as an informal document, manually executed procedure, or untracked script cannot provide reliable reuse, comparison, governance, or reconstruction.

Crucible represents Infrastructure Configurations as machine-readable, version-controlled Artifacts.

A machine-readable representation allows an authorized tool or workflow to process the Infrastructure Configuration without manual transcription.

Version Control preserves the configuration content associated with each revision and the relationships among successive revisions.

This representation provides a foundation for separately defined configuration management behaviors such as:

Configuration validationConfiguration comparisonConfiguration reviewConfiguration approvalConfiguration applicationConfiguration reuseConfiguration rollbackConfiguration retirementDrift detectionThe machine-readable, version-controlled representation supports:

Applies To

This requirement applies to:

Machine-readable representationsVersion ControlRevisionsRevision HistoryConfiguration ManagementProvenanceAuditabilityReproducibilityTraceability

Verification

Verification SHALL confirm that each tested Infrastructure Configuration uses a machine-readable representationVerification SHALL confirm that an authorized tool can process the machine-readable representation without requiring manual transcriptionVerification SHALL confirm that each tested Infrastructure Configuration is maintained by the applicable Version Control systemVerification SHALL confirm that the Version Control system preserves the content associated with each tested configuration revisionVerification SHALL confirm that the Version Control system preserves the relationship between successive configuration revisionsVerification SHALL confirm that an authorized user can retrieve a tested configuration revisionVerification SHALL confirm that the configuration record preserves the applicable Provenance and TraceabilityVerification may include:

Machine-readable format inspectionAutomated parsing testsAutomated processing testsVersion Control repository inspectionRepository history inspectionRevision content inspectionRevision relationship inspectionPrior revision retrieval testsThe verification record SHALL identify:

The tested Infrastructure ConfigurationThe machine-readable representationThe tool used to process the representationThe processing resultThe Version Control repositoryThe tested revisionThe preceding revision, when applicableThe succeeding revision, when applicableThe revision retrieval resultThe applicable ProvenanceThe observed resultsThe generated Evidence

Outgoing Traceability

This requirement refines:

This requirement operates within the conditions established by:

This requirement also relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference FR-CFG-002.

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.

ConOps Relationship

The Crucible Concept of Operations describes Phase 1 as a command-line utility invoked through CI/CD Pipeline steps.

The Phase 1 workflow uses machine-readable, version-controlled Infrastructure Configurations as controlled inputs for activities such as:

Selecting applicable configuration revisionsComposing selected BaselinesBuilding Machine ImagesPreparing deployment inputsPerforming Infrastructure DeploymentRecording the configuration revision associated with an executionPreserving execution results and EvidenceThe machine-readable, version-controlled representation provides the controlled Infrastructure Configuration input required by these activities.

Configuration validation, review, approval, authorization, application, and rollback remain separate functional behaviors subject to allocation across the remaining Configuration Management requirements.

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification that Crucible represents Infrastructure Configurations as machine-readable, version-controlled Artifacts.

Requirement Status

Draft

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

Notes for Editors

This requirement page should retain the stable requirement identifier FR-CFG-002.

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, configuration 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 validation, comparison, review, approval, authorization, application, rollback, and retirement obligations are allocated to FR-CFG-003 through FR-CFG-005 or 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-002#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.

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