====== FR-MC-005 — Edge 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 Edge Deployments.

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

This requirement derives from:

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

The Original Requirement states:

> //The system shall support edge deployments.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

FR-MC-005:

  * 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**
  * Capitalizes **Edge Deployments** as the named deployment capability

No other substantive normalization is required.

===== Rationale =====

An Edge Deployment places computing capabilities near a source or consumer of data, an operational process, a physical location, or another location where local processing provides an architectural benefit.

An Edge Deployment can involve:

  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machines]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Clusters]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workloads]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]]

This requirement establishes Edge Deployment behavior without prescribing:

  * The deployment subjects
  * The target Edge Environment
  * An edge platform
  * A device class
  * A Cloud Provider
  * A network architecture
  * An orchestration mechanism
  * A connectivity model
  * Disconnected operation
  * Air-gapped operation
  * Resource constraints
  * Synchronization behavior

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]]
  * Edge Deployments
  * Edge deployment workflows

===== Verification =====

Verification confirms that:

  - An Edge Deployment is selected for testing
  - The target of the tested deployment exhibits the characteristics defined for an Edge Deployment
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs the tested Edge Deployment
  - The deployed subjects can be identified in the target environment
  - The observed behavior demonstrates Edge Deployment

===== 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-005 as a leaf requirement.</todo>

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

<todo>Determine whether Edge Deployment requires a controlled definition in the shared Terms and Definitions corpus.</todo>

<todo>Determine whether Edge Environment requires a controlled definition in the shared Terms and Definitions corpus.</todo>

<todo>Determine whether separate requirements define connectivity, synchronization, resource constraints, and network isolation for Edge Deployments.</todo>

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

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

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 Edge Deployments.

Do not treat Edge Deployment as synonymous with deployment to a [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] or [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]].

Do not add specific deployment subjects, an Edge Environment, dependency capture, disconnected operation, synchronization, resource constraints, network isolation, platform, device, Provider, or connectivity 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-005#Statement&noheader&nofooter&noeditbtn}}
</code>

----

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