MO-005e — Infrastructure Baseline Reuse

Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines

Statement

Crucible SHALL apply the same approved Infrastructure Baseline revision to two or more Infrastructure Deployments.

Derived From

This requirement derives from:

The Original Requirement states:

The system SHALL establish infrastructure as a reusable and version-controlled asset.[C1]

MO-005e preserves the reuse intent of the Original Requirement by requiring Crucible to apply the same approved Infrastructure Baseline revision to multiple Infrastructure Deployments.

The separate requirements derived from MO-005 address:

Assessment

The Original Requirement describes infrastructure as reusable but does not identify the behavior that demonstrates reuse.

The phrase reusable asset does not identify:

The managed subject that is reusedThe revision that is reusedThe approval condition applicable to that revisionThe operation that constitutes reuseThe minimum number of Infrastructure Deployments needed to demonstrate reuseWhether reuse applies to the same revision or different revisionsThe relationship between reuse and modification of approved baseline contentThe Evidence required to demonstrate reuseMO-005e:

Identifies Crucible as the responsible actorIdentifies an approved Infrastructure Baseline revision as the reused subjectDefines reuse as application of the same revision to multiple Infrastructure DeploymentsEstablishes two Infrastructure Deployments as the minimum verification thresholdSeparates reuse from selection, Version Control, immutability, and deployment traceability

Rationale

Reuse occurs when Crucible applies the same approved Infrastructure Baseline revision to more than one Infrastructure Deployment.

Reuse supports:

Consistent infrastructure compositionReduction of duplicated configuration effortRepeatable deployment processesComparison of Infrastructure Deployments created from the same baseline revisionReproduction of previously deployed infrastructureControlled deployment across multiple operational environmentsControlled deployment across multiple Deployment PlatformsPreservation of approved infrastructure configurationsMaintenance of ProvenanceMaintenance of TraceabilityGeneration of auditable EvidenceThe minimum threshold of two Infrastructure Deployments distinguishes demonstrated reuse from a single application of an Infrastructure Baseline revision.

The Infrastructure Deployments can differ in deployment instance, location, operational environment, Deployment Platform, execution time, or intended use, provided that Crucible applies the same approved Infrastructure Baseline revision.

This requirement does not require the Infrastructure Deployments to produce identical platform-specific results. Applicable Deployment Platform parameters and Provider Implementations can produce permitted differences while preserving the selected Infrastructure Baseline revision.

This requirement does not prohibit modification of approved baseline content. MO-005f establishes approved baseline immutability.

This requirement does not require each Infrastructure Deployment to record the applied baseline identifiers. MO-005g establishes deployment traceability.

Applies To

This requirement applies to:

Approved Infrastructure Baseline revisionsInfrastructure DeploymentsArtifact identifiersRevision identifiersApproval recordsSelection recordsDeployment recordsDeployment PlatformsOperational environmentsDeployment parametersProvider ImplementationsArtifact catalog recordsArtifact repositoriesEvidenceProvenanceTraceability

Verification

Verification confirms that:

The approved Infrastructure Baseline revision is identifiedTwo or more Infrastructure Deployments are identifiedCrucible applies the same approved Infrastructure Baseline revision to each identified Infrastructure DeploymentThe applied Artifact identifier is the same for each identified Infrastructure DeploymentThe applied revision identifier is the same for each identified Infrastructure DeploymentEach application completes with an identified resultThe generated Evidence demonstrates reuse of the same approved revisionVerification includes:

Infrastructure Baseline inspectionApproval-record inspectionArtifact identifier inspectionRevision identifier inspectionInfrastructure Deployment inspectionBaseline application testingMultiple-deployment testingDeployment-record comparisonApplied-content comparisonEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

The approved Infrastructure BaselineThe stable Artifact identifierThe approved revision identifierThe approval statusEach Infrastructure Deployment used to demonstrate reuseThe application result for each Infrastructure DeploymentThe Artifact identifier applied to each Infrastructure DeploymentThe revision identifier applied to each Infrastructure DeploymentEach identified difference attributable to deployment-specific parametersEach identified failure or exceptionThe observed resultThe generated Evidence

Requirements Realized By

This requirement is realized by:

Related Architecture Sections

Referenced By

The following pages reference this requirement:

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification that the current Crucible implementation applies the same approved Infrastructure Baseline revision to two or more Infrastructure Deployments.

Requirement Status

Draft

This requirement derives from MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.

Notes for Editors

This requirement page should retain the stable requirement identifier MO-005e.

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

Changes to the Statement should preserve the Infrastructure Baseline reuse intent derived from MO-005.

The reuse record should identify:

The stable Infrastructure Baseline Artifact identifierThe applied revision identifierThe approval status of the applied revisionEach Infrastructure DeploymentThe application date and timeThe operational environmentThe Deployment PlatformThe applicable deployment-specific parametersThe application resultThe associated ProvenanceThe associated TraceabilityThe supporting EvidenceMaterial changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.

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

{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005e#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.