MO-003b — Common Crucible Description

Go to MO-003 — Cloud-Agnostic Deployment

Statement

Crucible SHALL use the same identified version of the platform-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.[C3]

MO-003b preserves the portion of the Original Requirement that requires common platform-independent deployment intent across the selected Deployment Platforms.

The separate requirements derived from MO-003 address:

Assessment

The Original Requirement does not identify the deployment information that remains common across Cloud Providers or Deployment Platforms.

The phrase cloud-agnostic deployment capabilities does not identify:

The platform-independent deployment intentThe Artifact that records the deployment intentThe version of that ArtifactThe Deployment Platforms to which the common deployment intent appliesThe distinction between changes to platform-independent intent and changes to platform-specific informationMO-003b:

Identifies the Crucible Description as the source of platform-independent deployment intentRequires use of the same identified Crucible Description version across the selected Deployment PlatformsPrevents a change of target Deployment Platform from implicitly creating a different platform-independent deployment intentSeparates common Crucible Description use from cross-platform deployment, common Infrastructure Baseline use, and provider-specific dependency limitation

Rationale

A common platform-independent Crucible Description allows one deployment intent to apply across multiple Deployment Platforms.

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

Using the same identified version supports:

Consistent deployment intentControlled comparison of deployment resultsProvenanceTraceabilityChange controlDetection of provider-specific information within platform-independent contentReuse across supported Deployment PlatformsThe requirement uses an identified version rather than the unqualified word same. The identifier and version establish the specific Crucible Description used for each deployment.

Platform-specific values required by a target Deployment Platform remain separate from the platform-independent Crucible Description. The applicable provider-specific mechanisms translate the common deployment intent for the target platform.

This requirement does not require use of the same Infrastructure Baseline. MO-003c establishes that requirement.

Applies To

This requirement applies to:

Verification

Verification confirms that:

Two or more selected Deployment Platforms are identifiedEach deployment uses a Crucible Description with the same identifierEach deployment uses the same identified version of the Crucible DescriptionThe Crucible Description contains platform-independent deployment intentChanging the selected Deployment Platform does not require modification of the identified Crucible Description versionPlatform-specific values remain separate from the platform-independent Crucible DescriptionThe deployment records identify the Crucible Description identifier and version used for each Deployment PlatformVerification includes:

Crucible Description inspectionCrucible Description identifier comparisonCrucible Description version comparisonArtifact Representation comparisonCryptographic digest inspectionPlatform-independent information inspectionPlatform-specific information inspectionCross-platform deployment testsDeployment-record inspectionProvenance inspectionTraceability inspectionEvidence inspectionThe verification record identifies:

The selected Deployment PlatformsThe Crucible Description identifierThe Crucible Description versionThe applicable Crucible Description Artifact RepresentationThe cryptographic digest of the applicable Artifact RepresentationThe platform-independent deployment intentThe platform-specific information used for each Deployment PlatformThe deployment result for each Deployment PlatformAny detected modification to the Crucible DescriptionThe 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 platform-independent Crucible Description.

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-003b.

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

Changes to the Statement SHALL preserve the common platform-independent Crucible Description intent derived from MO-003.

The applicable deployment records should identify:

The Crucible Description identifierThe Crucible Description versionThe applicable Artifact RepresentationThe cryptographic digestThe selected Deployment PlatformThe applicable Provider ImplementationThe platform-specific information used for the deploymentThe deployment resultThe 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-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.