MO-003

Go to Mission Objectives

Statement

Crucible SHALL deploy an Infrastructure Baseline to each supported Deployment Platform from the same platform independent Crucible Description, except for explicitly identified platform specific parameters.

Source Statement

The system SHALL provide cloud-agnostic deployment capabilities.

Source

Crucible System Requirements Specification, Version 1.1 Draft, Mission Objectives, MO-003.

Assessment

The source statement expresses the approved mission objective but does not define a fully testable requirement.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system nameProvide is a weak verb that does not identify the behavior Crucible performsCloud agnostic does not identify the characteristics required for conformanceDeployment capabilities does not identify the deployable artifact, deployment inputs, target platforms, or required outcomeThe source statement does not distinguish platform independent information from platform specific informationThe source statement does not define how verification determines whether cloud specific behavior has leaked into platform independent componentsThe normalized Statement replaces the weak verb with deploy, identifies the deployable Infrastructure Baseline, identifies the common input, and bounds permitted platform specific variation.

Rationale

Organizations may deploy equivalent infrastructure across commercial cloud, private cloud, on premises, edge, and disconnected environments.

Without an explicit separation between platform independent and platform specific information, deployment logic becomes coupled to individual providers. Such coupling increases migration effort, produces inconsistent deployment behavior, and allows provider specific implementation details to spread through the core architecture.

Crucible addresses this problem through:

Platform independent deployment informationExplicitly identified platform specific parametersA provider abstractionProvider implementationsConsistent deployment results across supported Deployment PlatformsThis separation allows the same deployment intent to target multiple platforms without embedding provider specific behavior in platform independent Crucible components.

Applies To

This requirement applies to:

Verification

Verification SHALL confirm that the same platform independent Crucible Description can identify deployments for at least two supported Deployment PlatformsVerification SHALL confirm that each tested deployment uses the same Infrastructure BaselineVerification SHALL confirm that differences between tested deployments are limited to explicitly identified platform specific parametersVerification SHALL confirm that platform independent Crucible components do not contain provider specific deployment behaviorVerification SHALL confirm that each provider implementation conforms to the applicable provider contractVerification SHALL confirm that each tested deployment produces an environment that satisfies the common acceptance criteriaVerification SHALL confirm that each tested deployment satisfies the platform specific acceptance criteria for the target Deployment PlatformVerification SHALL confirm that changing the target Deployment Platform does not require modification of the platform independent deployment intentVerification may include:

Cross platform deployment testsProvider contract testsProvider implementation testsCrucible Description comparisonInfrastructure Baseline comparisonPlatform specific parameter inspectionCore dependency analysisProvider dependency analysisDeployment result comparisonEnd-to-end CI/CD Pipeline testsThe verification record SHALL identify:

The tested Crucible DescriptionThe tested Infrastructure BaselineThe tested Deployment PlatformsThe common platform independent informationThe platform specific parametersThe applicable provider contractThe provider implementationsThe common acceptance criteriaThe platform specific acceptance criteriaThe observed deployment resultsThe generated Evidence

Outgoing Traceability

This requirement is realized by:

The phrase Enable cloud portability is retained only as the title of the source requirement. The KVP-006 requirement statement should undergo the same SDA and CWE assessment because enable is weak.

This requirement also relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference `MO-003`.

Incoming traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship.

ConOps Relationship

The Crucible Concept of Operations describes Phase 1 as a command-line utility invoked through CI/CD Pipeline steps.

The Phase 1 workflow uses declarative inputs and currently orchestrates external deployment tools. The target architecture separates platform independent Crucible behavior from provider specific behavior.

The architecture uses a provider contract as the boundary between the core system and individual Deployment Platforms. Each provider implementation performs the behavior required for its target platform without introducing provider specific dependencies into platform independent core components.

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification across at least two supported Deployment Platforms using the same platform independent deployment intent.

Requirement Status

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.

Notes for Editors

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

Changes to the Statement SHALL preserve the approved intent of the source requirement.

Material changes should receive review and should update the related outbound traceability, verification criteria, acceptance criteria, and source records.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.

Do not rename this page once it has been cited externally unless a redirect or move plan is in place.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.