====== C.3.4 Multi-Cloud Management ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to Crucible Functional Requirements]]

The Multi-Cloud Management [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|requirements]] define how [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] separates [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_information|Platform Independent Information]] from [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_information|Platform Specific Information]], incorporates provider-specific extensions, supports deployment across cloud providers, and operates across hybrid-cloud and edge environments.

Together, these requirements establish [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independence|Platform Independence]] and provider realization behavior that contributes to [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_portability|Cloud Portability]], provider substitution, and consistent deployment outcomes across [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementations]].

===== Contents =====

{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management#1|js navbar nocookie maxjs#1 id#crucible_multi_cloud_management_requirements_nav}}

===== Notes for Editors =====

The individual requirement pages should retain the stable identifiers ''FR-MC-001'' through ''FR-MC-005''.

Individual requirement pages are leaf nodes and should not include a trailing '':start'' in their namespaces.

The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.

Normalized Statements should use direct, testable behavior and should distinguish Platform Independent Information from Platform Specific Information and [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_parameter|Platform Specific Parameters]].

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] should use the wiki Backlinks function rather than a manually maintained list.

To reference a requirement Statement from another wiki page, insert:

<code dokuwiki>
{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}
</code>

Replace ''<namespace>'' with the namespace of the requirement leaf page.

The section name following ''#'' SHALL match the section heading verbatim on the requirement page.

Do not rename a requirement page after an external citation unless a redirect or move plan is in place.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>