FR-CFG-003 — Reusable Infrastructure Blueprints

Go to Crucible Configuration Management Requirements

Statement

Crucible SHALL apply the same Infrastructure Blueprint to two or more Infrastructure Environments without modifying the reusable blueprint content.

Source Statement

The system SHALL support reusable infrastructure blueprints.

Source

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

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 blueprint does not identify how the blueprint demonstrates reuseReusable does not identify the minimum number of applications required to demonstrate reuseThe source statement does not distinguish application of a blueprint from modification of the reusable blueprint contentThe source statement does not identify the observable result used to verify reuseThe normalized Statement:

Replaces The system with the defined system nameReplaces support with the direct behavior applyIdentifies the Infrastructure Blueprint as the reusable specificationDefines reuse as application of the same blueprint to two or more Infrastructure EnvironmentsDistinguishes reuse from modification of the reusable blueprint contentThe normalized Statement does not introduce blueprint approval, validation, deployment, acceptance, revision-history, or traceability obligations. Separate requirements govern those behaviors when required.

Rationale

An Infrastructure Blueprint specifies reusable infrastructure resources, relationships, configurable properties, and constraints applicable to multiple Infrastructure Environments.

Without a reusable blueprint, an organization may recreate similar infrastructure definitions for each environment. Repeated recreation increases engineering effort and can produce inconsistent infrastructure representations.

Reuse requires the same blueprint content to remain applicable across two or more environments.

Environment-specific configuration may differ without changing the reusable blueprint content. Those differences may appear in separate:

Input valuesParametersOverridesEnvironment recordsApplying the same blueprint to multiple environments contributes to:

Reduced configuration duplicationConsistent infrastructure structureReduced engineering effortControlled environment-specific variationConfiguration reuseReproducibility

Applies To

This requirement applies to:

Reusable blueprint contentBlueprint applicationInfrastructure EnvironmentsInfrastructure ConfigurationsEnvironment-specific values

Verification

Verification SHALL confirm that Crucible applies the same tested Infrastructure Blueprint to at least two Infrastructure EnvironmentsVerification SHALL confirm that each tested application uses equivalent reusable blueprint contentVerification SHALL confirm that applying the Infrastructure Blueprint does not modify the reusable blueprint contentVerification SHALL confirm that environment-specific values remain separate from the reusable blueprint contentVerification may include:

Infrastructure Blueprint inspectionRepeated blueprint application testsMulti-environment application testsBlueprint content comparisonEnvironment-specific value inspectionThe verification record SHALL identify:

The tested Infrastructure BlueprintThe reusable blueprint contentThe tested Infrastructure EnvironmentsThe environment-specific valuesThe blueprint content comparison 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-003.

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 the composition and reuse of infrastructure content within a CI/CD Pipeline workspace.

A workflow may apply the same Infrastructure Blueprint to multiple Infrastructure Environments while supplying environment-specific values separately.

This separation preserves reusable infrastructure structure while allowing each environment to define the values required for its own context.

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification that Crucible applies the same Infrastructure Blueprint to two or more Infrastructure Environments without modifying the reusable blueprint content.

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

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 blueprint reuse and preservation of reusable blueprint content.

Blueprint approval, validation, deployment, acceptance, revision history, and traceability should not be introduced as normative behavior on this page unless the Statement changes through an approved requirements process.

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-003#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.