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 or observable resultThe source statement does not identify whether the infrastructure representation must be machine-readableThe source statement does not identify whether the representation must be controlled through Version ControlThe source statement does not distinguish artifact representation from revision-history preservationThe normalized Statement:

Replaces The system with the defined system nameReplaces support with the direct behavior representIdentifies the Infrastructure Configuration as the represented informationIdentifies a machine-readable Artifact as the required representationRequires the Artifact to remain under Version ControlThis requirement governs the representation and control of the Infrastructure Configuration Artifact. FR-CFG-005 separately governs preservation of configuration revisions and the relationships among successive revisions.

Rationale

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

An Infrastructure Configuration that exists only as an informal document, manually executed procedure, or untracked script cannot serve as a consistently processable and controlled infrastructure definition.

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

Version Control places the Infrastructure Configuration Artifact under controlled revision management.

The machine-readable, version-controlled representation provides a foundation for separately defined behaviors such as:

Configuration reuseConfiguration inheritanceConfiguration revision preservationConfiguration comparisonInfrastructure deploymentEnvironment reconstructionThis representation contributes to:

Consistent automated processingControlled configuration changeConfiguration reuseReproducibilityProvenanceTraceability

Applies To

This requirement applies to:

Machine-readable representationsVersion Control

Verification

Verification SHALL confirm that each tested Infrastructure Configuration exists as an identifiable ArtifactVerification SHALL confirm that each tested Infrastructure Configuration Artifact uses a machine-readable representationVerification SHALL confirm that an authorized tool can parse the machine-readable representation without manual transcriptionVerification SHALL confirm that each tested Infrastructure Configuration Artifact is maintained under the applicable Version Control systemVerification SHALL confirm that the Version Control system assigns an identifiable revision to the tested Infrastructure Configuration ArtifactVerification SHALL confirm that an authorized user or process can retrieve the identified revisionVerification may include:

Artifact inspectionMachine-readable format inspectionAutomated parsing testsVersion Control repository inspectionRevision identification testsRevision retrieval testsThe verification record SHALL identify:

The tested Infrastructure ConfigurationThe corresponding ArtifactThe machine-readable representationThe tool used to parse the representationThe parsing resultThe applicable Version Control systemThe tested revision identifierThe revision retrieval resultThe 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 Configuration Artifacts as controlled inputs for activities such as:

Selecting an identified configuration revisionComposing selected BaselinesBuilding Machine ImagesPreparing deployment inputsPerforming Infrastructure DeploymentThe machine-readable representation allows automated processing. Version Control provides controlled identification and retrieval of the Artifact revision used by the workflow.

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification that Crucible represents each Infrastructure Configuration as a machine-readable, version-controlled Artifact.

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, and source records.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

Verification criteria should test only the Artifact representation, machine readability, and Version Control behavior defined by the Statement.

Revision-content preservation and relationships among successive revisions belong to FR-CFG-005 and should not be duplicated as normative behavior on this page.

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.