MO-003b — Provider-Independent Crucible Description

Go to MO-003 — Cloud-Agnostic Deployment

Statement

Crucible SHALL use the same identified version of the provider-independent Crucible Description 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-003b preserves the portion of the Original Requirement that requires common provider-independent deployment intent across the selected Deployment Platforms.

The separate requirements derived from MO-003 address:

Rationale

A provider-independent Crucible Description allows the same deployment intent to apply across multiple Deployment Platforms.

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

The Crucible Description should express the required deployment without embedding the proprietary interfaces, services, data formats, software development kits, or operational mechanisms of a particular Cloud Provider.

Platform-specific information remains separate from the provider-independent Crucible Description. A Provider Implementation translates the provider-independent deployment intent into mechanisms supported by the selected Deployment Platform.

Using the same identified version supports:

Consistent deployment intentControlled comparison of deployment resultsChange controlDetection of provider-specific information within provider-independent contentReuse across supported Deployment PlatformsProvenanceTraceabilityThis requirement does not require use of the same Infrastructure Baseline. MO-003c addresses that outcome.

Applies To

This requirement applies to:

Crucible Description identifiersCrucible Description versionsPlatform Independent InformationPlatform Specific InformationPlatform Specific ParametersDeployment PlatformsProvider ContractsProvider ImplementationsInfrastructure DeploymentsArtifactsEvidenceProvenanceTraceability

Verification

Verification confirms that:

Two or more selected Deployment Platforms are identifiedThe provider-independent Crucible Description is identifiedEach deployment uses a Crucible Description with the same identifierEach deployment uses the same identified version of the Crucible DescriptionThe Crucible Description contains provider-independent deployment intentChanging the selected Deployment Platform does not require modification of the identified Crucible Description versionPlatform Specific Information remains separate from the provider-independent Crucible DescriptionEach deployment record identifies the Crucible Description identifier and version used for the selected Deployment PlatformThe verification record preserves Traceability among the Crucible Description, 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-003b.

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 Crucible Description as the common source of deployment intentUse of the same identified Crucible Description version across the selected Deployment PlatformsSeparation of provider-independent and provider-specific informationThe 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-003b#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.