====== FR-MC-004 — Hybrid-Cloud Deployments ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:start|Go to Crucible Multi-Cloud Management Requirements]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployments]].

===== Derived From =====

This requirement derives from:

  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-004

The Original Requirement states:

> //The system shall support [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployments]].//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

FR-MC-004:

  * Replaces **The system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * Changes **shall** to the established uppercase normative form **SHALL**
  * Replaces the weak verb **support** with the observable behavior **perform**
  * Links **Hybrid-Cloud Deployments** to the controlling definition

No other substantive normalization is required.

===== Rationale =====

A [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployment]] combines deployment subjects across cloud and non-cloud environments.

A Hybrid-Cloud Deployment can include:

  * A public-cloud environment and an on-premises environment
  * A provider-managed cloud environment and a privately operated environment
  * Cloud-hosted services and locally hosted workloads
  * Cloud computing resources and edge computing resources

The participating environments can differ in administrative authority, network accessibility, security controls, resource models, Provider interfaces, operational constraints, and compliance obligations.

This requirement establishes Hybrid-Cloud Deployment behavior without prescribing:

  * The participating environments
  * The deployment subjects assigned to each environment
  * Cross-environment connectivity
  * Identity federation
  * Security-boundary behavior
  * Synchronization
  * Workload placement
  * A particular Cloud Provider
  * A particular network or orchestration technology

Separate requirements, architecture specifications, workflows, or policies define those subjects and behaviors.

===== 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:h:hybrid-cloud_deployment|Hybrid-Cloud Deployments]]
  * Cloud environments
  * Non-cloud environments
  * Hybrid deployment workflows

===== Verification =====

Verification confirms that:

  - A Hybrid-Cloud Deployment is selected for testing
  - The tested deployment includes at least one cloud environment
  - The tested deployment includes at least one non-cloud environment
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs the tested [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployment]]
  - Deployment subjects are realized in the participating environments
  - The observed behavior demonstrates deployment across cloud and non-cloud environments

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:02-crusible}}

===== Implementation Status =====

Implemented and Verified

===== Requirement Status =====

<todo>Review and approve FR-MC-004 as a leaf requirement.</todo>

----
===== Issues =====

<todo>Confirm that Hybrid-Cloud Deployment has a controlled definition in the shared Terms and Definitions corpus.</todo>

<todo>Determine whether separate requirements define cross-environment connectivity, security, identity federation, synchronization, and workload placement.</todo>

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

This requirement page retains the stable requirement identifier ''FR-MC-004''.

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

The Statement preserves the approved source intent by requiring Crucible to perform Hybrid-Cloud Deployments.

Do not add specific cloud and non-cloud Infrastructure Environments, workload placement, connectivity, security, identity federation, synchronization, Provider, network, or orchestration obligations unless the controlling requirement changes through an approved requirements process.

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

<code dokuwiki>
{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-004#Statement&noheader&nofooter&noeditbtn}}
</code>

----

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