MO-003c — Provider-Independent Infrastructure Baseline

Go to MO-003 — Cloud-Agnostic Deployment

Statement

Crucible SHALL use the same identified version of the provider-independent 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.[C2]

MO-003c preserves the portion of the Original Requirement that requires common provider-independent infrastructure requirements across the selected Deployment Platforms.

The separate requirements derived from MO-003 address:

Rationale

A provider-independent Infrastructure Baseline establishes consistent infrastructure requirements across multiple Deployment Platforms.

Using the same identified version prevents a change of Deployment Platform from implicitly changing the provider-independent infrastructure requirements.

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

Using the same identified version supports:

Consistent infrastructure requirementsControlled comparison of deployment resultsChange controlDetection of platform-specific changes to provider-independent baseline requirementsReuse across supported Deployment PlatformsProvenanceTraceabilityThis requirement does not require use of the same Crucible Description. MO-003b addresses that outcome.

Applies To

This requirement applies to:

Infrastructure Baseline identifiersInfrastructure Baseline versionsPlatform Independent InformationPlatform Specific InformationDeployment PlatformsProvider ContractsProvider ImplementationsPlatform Specific ParametersInfrastructure DeploymentsInfrastructure EnvironmentsArtifactsEvidenceProvenanceTraceability

Verification

Verification confirms that:

Two or more selected Deployment Platforms are identifiedThe provider-independent Infrastructure Baseline is identifiedEach deployment uses an Infrastructure Baseline with the same identifierEach deployment uses the same identified version of the Infrastructure BaselineThe Infrastructure Baseline contains provider-independent infrastructure requirementsChanging the selected Deployment Platform does not require modification of the identified Infrastructure Baseline versionPlatform Specific Information remains separate from the provider-independent Infrastructure BaselinePlatform-specific implementation mechanisms do not alter the requirements established by the Infrastructure BaselineEach deployment record identifies the Infrastructure Baseline identifier and version used for the selected Deployment PlatformThe verification record preserves Traceability among the Infrastructure Baseline, selected Deployment Platform, Provider Implementation, platform-specific information, and deployment result

Referenced By

The following pages reference this requirement:

Delivery Phase

Implemented and Verified

Implementation Status

Requirement Status

Issues

The following unresolved issues affect this requirement:

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.

The parent MO-003 page is a non-leaf page and retains a trailing :start in its namespace.

Changes to the Statement should preserve:

as the responsible actorThe provider-independent Infrastructure Baseline as the common source of infrastructure requirementsUse of the same identified Infrastructure Baseline version across the selected Deployment PlatformsSeparation of provider-independent baseline requirements and provider-specific implementation detailsThe unresolved boundary between provider-independent and provider-specific information should remain recorded in the Issues section until a controlling source defines it.

Material changes should receive review and should update the verification criteria, source records, and Issues section.

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.