Table of Contents

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.

Derived From

This requirement derives from:

The Original Requirement states:

The system SHALL support reusable infrastructure blueprints.[C1]

FR-CFG-003:

Rationale

An Infrastructure Blueprint provides a reusable definition of infrastructure structure, relationships, configurable properties, and constraints.

Applying the same Infrastructure Blueprint to multiple Infrastructure Environments reduces duplicated definitions and promotes consistent infrastructure structure.

Environment-specific values, parameters, or controlled overrides allow each Infrastructure Environment to use the reusable Infrastructure Blueprint within its own operational context.

Applies To

This requirement applies to:

Verification

Verification confirms that:

  1. A tested Infrastructure Blueprint is selected for reuse
  2. Crucible applies the same tested Infrastructure Blueprint to at least two Infrastructure Environments
  3. Each application identifies the Infrastructure Environment to which the Infrastructure Blueprint applies
  4. Each Infrastructure Environment receives the infrastructure definition provided by the tested Infrastructure Blueprint
  5. Environment-specific values, parameters, or controlled overrides do not prevent identification of the common Infrastructure Blueprint

Referenced By

The following pages reference this requirement:

Implementation Status

Implemented and Verified

Requirement Status

Review and approve FR-CFG-003 as a leaf requirement.


Issues

Determine whether reusable Infrastructure Blueprints permit controlled overrides and identify the rules governing those overrides.


Notes for Editors

This requirement page retains the stable requirement identifier FR-CFG-003.

This page is a leaf requirement page and omits a trailing :start from its namespace.

The Statement preserves the approved source intent by requiring reuse of the same Infrastructure Blueprint across two or more Infrastructure Environments.

Do not add blueprint approval, validation, deployment, acceptance, revision-history, or traceability obligations to the Statement unless the controlling requirement changes through an approved requirements process.

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}}

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