====== MO-003a — Cross-Platform Deployment ====== [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:start|Go to MO-003 — Cloud-Agnostic Deployment]] ===== Statement ===== [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL deploy an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] to two or more supported [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platforms]]. ===== Derived From ===== This requirement derives from: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:start|MO-003 — Cloud-Agnostic Deployment]] The Original Requirement states: > //The system SHALL provide cloud-agnostic deployment capabilities.//[[dido:02-crusible:99-annexes:annex-b:cr-002|[C2]]] MO-003a preserves the portion of the Original Requirement that requires [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] to deploy Infrastructure Environments across multiple Deployment Platforms. The separate requirements derived from MO-003 address: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003b|MO-003b — Provider-Independent Crucible Description]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003c|MO-003c — Provider-Independent Infrastructure Baseline]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003d|MO-003d — Limitation of Provider-Specific Dependencies]] ===== Rationale ===== [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism|Cloud Agnosticism]] requires Crucible to operate across more than one Deployment Platform. Deployment to two or more supported Deployment Platforms provides the minimum observable basis for evaluating cross-platform deployment. A supported Deployment Platform requires an identified and approved mechanism through which Crucible performs the deployment. Cross-platform deployment does not alone establish complete Cloud Agnosticism. The other requirements derived from MO-003 address provider-independent deployment information and limitation of provider-specific dependencies. ===== Applies To ===== This requirement applies to: * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] * [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism|Cloud Agnosticism]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platforms]] * Supported Deployment Platforms * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contracts]] * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementations]] * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_parameter|Platform Specific Parameters]] * [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]] * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] ===== Verification ===== Verification confirms that: - Two or more supported [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platforms]] are identified - The support criteria for each Deployment Platform are identified - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] to each identified Deployment Platform - Each Infrastructure Deployment creates an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] - Each deployment result identifies the target Deployment Platform - Each deployment result identifies the [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementation]] used for the Deployment Platform - Each resulting Infrastructure Environment satisfies the deployment acceptance criteria established for the target Deployment Platform - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Controlled Inputs, target Deployment Platform, Provider Implementation, Infrastructure Deployment, and resulting Infrastructure Environment ===== Referenced By ===== The following pages reference this requirement: {{backlinks>.#dido:02-crusible}} ===== Delivery Phase ===== Implemented and Verified ===== Implementation Status ===== Assess whether the current Crucible implementation deploys an Infrastructure Environment to two or more supported Deployment Platforms. ===== Requirement Status ===== Review and accept MO-003a as a proposed derived requirement created from the evaluation and decomposition of MO-003 in the Crucible System Requirements Specification, Version 1.1 Draft. ---- ===== Issues ===== The following unresolved issues affect this requirement: Identify the Deployment Platforms that Crucible supports. Define the criteria used to determine that a Deployment Platform is supported. Confirm that deployment to two supported Deployment Platforms provides sufficient minimum evidence of cross-platform deployment. Identify the deployment acceptance criteria for each supported Deployment Platform. Identify the controlling source that approves the Provider Contract and Provider Implementation used for each supported Deployment Platform. ---- ===== Notes for Editors ===== This requirement page should retain the stable requirement identifier ''MO-003a''. 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: * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor * Deployment of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] as the required outcome * Deployment to two or more supported [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platforms]] as the cross-platform obligation The criteria for a supported Deployment Platform should identify: * The Deployment Platform * The approved [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contract]] * The approved [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementation]] * The supported [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_parameter|Platform Specific Parameters]] * The deployment acceptance criteria * The required [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] 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-003a#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.