MO-003c — Common Infrastructure Baseline

Go to MO-003 — Cloud-Agnostic Deployment

Statement

Crucible SHALL use the same identified version of the Infrastructure Baseline for each selected Deployment Platform.

Derived From

This requirement derives from:

The Original Requirement states:

The system SHALL provide cloud-agnostic deployment capabilities.[C3]

MO-003c preserves the portion of the Original Requirement that requires a common Infrastructure Baseline across the selected Deployment Platforms.

The separate requirements derived from MO-003 address:

Assessment

The Original Requirement does not identify the infrastructure requirements that remain common across Cloud Providers or Deployment Platforms.

The phrase cloud-agnostic deployment capabilities does not identify:

The common Infrastructure BaselineThe version of the Infrastructure BaselineThe Deployment Platforms to which the Infrastructure Baseline appliesThe distinction between baseline requirements and platform-specific implementation detailsThe criteria used to determine whether the same Infrastructure Baseline was applied to each deploymentMO-003c:

Identifies the Infrastructure Baseline as the common source of infrastructure requirementsRequires use of the same identified Infrastructure Baseline version across the selected Deployment PlatformsPrevents a change of target Deployment Platform from implicitly changing the common infrastructure requirementsSeparates common Infrastructure Baseline use from cross-platform deployment, common Crucible Description use, and provider-specific dependency limitation

Rationale

A common Infrastructure Baseline establishes consistent infrastructure requirements across multiple Deployment Platforms.

The Infrastructure Baseline defines the required infrastructure characteristics independently of the provider-specific mechanisms used to realize those characteristics.

Using the same identified version supports:

Consistent infrastructure requirementsControlled comparison of deployment resultsProvenanceTraceabilityChange controlCross-platform evaluationDetection of platform-specific changes to common baseline requirementsReuse across supported Deployment PlatformsThe requirement uses an identified version rather than the unqualified word same. The identifier and version establish the specific Infrastructure Baseline applied to each deployment.

Provider-specific implementations can realize the common Infrastructure Baseline through different platform mechanisms. Those mechanisms do not change the requirements established by the identified Infrastructure Baseline.

This requirement does not require use of the same Crucible Description. MO-003b establishes that requirement.

Applies To

This requirement applies to:

Verification

Verification confirms that:

Two or more selected Deployment Platforms are identifiedEach deployment uses an Infrastructure Baseline with the same identifierEach deployment uses the same identified version of the Infrastructure BaselineThe Infrastructure Baseline defines common infrastructure requirementsChanging the selected Deployment Platform does not require modification of the identified Infrastructure Baseline versionPlatform-specific implementation mechanisms do not alter the requirements established by the Infrastructure BaselineThe deployment records identify the Infrastructure Baseline identifier and version used for each Deployment PlatformVerification includes:

Infrastructure Baseline inspectionInfrastructure Baseline identifier comparisonInfrastructure Baseline version comparisonArtifact Representation comparisonCryptographic digest inspectionPlatform-independent information inspectionPlatform-specific information inspectionCross-platform deployment testsResulting Infrastructure Environment comparisonDeployment-record inspectionProvenance inspectionTraceability inspectionEvidence inspectionThe verification record identifies:

The selected Deployment PlatformsThe Infrastructure Baseline identifierThe Infrastructure Baseline versionThe applicable Infrastructure Baseline Artifact RepresentationThe cryptographic digest of the applicable Artifact RepresentationThe common infrastructure requirementsThe platform-specific implementation mechanisms used for each Deployment PlatformThe deployment result for each Deployment PlatformThe resulting Infrastructure Environment for each Deployment PlatformAny detected modification to the Infrastructure BaselineThe 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 deployments to the selected Deployment Platforms use the same identified version of the Infrastructure Baseline.

Requirement Status

Draft

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

Notes for Editors

This requirement page should retain the stable requirement identifier MO-003c.

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

Changes to the Statement SHALL preserve the common Infrastructure Baseline intent derived from MO-003.

The applicable deployment records should identify:

The Infrastructure Baseline identifierThe Infrastructure Baseline versionThe applicable Artifact RepresentationThe cryptographic digestThe selected Deployment PlatformThe applicable Provider ImplementationThe platform-specific implementation mechanisms used for the deploymentThe deployment resultThe resulting Infrastructure EnvironmentThe 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-003:mo-003c#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.