FR-MC-005 — Edge Deployments

Go to Crucible Multi-Cloud Management Requirements

Statement

Crucible SHALL deploy identified deployment subjects to an Edge Environment.

Source Statement

The system shall support edge deployments.

Source

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

Assessment

The source statement identifies a target deployment context but does not state the required deployment behavior.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system nameshall does not follow the established uppercase normative conventionSupport is a weak verbEdge deployment does not identify the deployment subjectsEdge does not identify a controlled target-environment conceptThe source statement does not prescribe an edge platform, device class, provider, network architecture, orchestration mechanism, or connectivity modelThe normalized Statement:

Replaces The system with CrucibleReplaces support with the direct behavior deployIdentifies deployment subjectsIdentifies an Edge Environment as the targetPreserves implementation independenceEdge Environment and possibly Edge Deployment should receive glossary definitions. Defining Edge Environment is the higher priority because it identifies the deployment target.

Rationale

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

Edge deployment subjects may include:

ConfigurationSecurity controlsMonitoring capabilitiesAn Edge Environment may operate with:

Limited network connectivityIntermittent connectivityRestricted bandwidthLimited computing capacityLimited storage capacityLocation-specific security controlsLocal operational authorityLow-latency processing requirementsFR-MC-005 does not independently require disconnected operation. The Air-Gapped Operations requirements govern disconnected and Air-Gapped Environment behavior.

Applies To

This requirement applies to:

Edge EnvironmentsEdge DeploymentsDeployment subjectsInfrastructure ResourcesVirtual MachinesKubernetes ClustersContainerized WorkloadsPlatform ServicesEdge deployment workflows

Verification

Verification SHALL confirm that the tested target is identified as an Edge EnvironmentVerification SHALL confirm that the deployment subjects assigned to the Edge Environment are identifiedVerification SHALL confirm that Crucible deploys the identified subjects to the Edge EnvironmentVerification SHALL confirm that the resulting deployment satisfies the applicable Edge Environment Acceptance CriteriaVerification may include:

Edge Deployment testingTarget-environment inspectionLimited-connectivity testingResource-constraint testingDeployment-state inspectionAcceptance testingDeployment-log inspectionThe verification record SHALL identify:

The Edge EnvironmentThe deployed subjectsThe applicable environment constraintsThe applicable Acceptance CriteriaThe deployment operationThe observed deployment resultThe generated Evidence

Outgoing Traceability

This requirement realizes:

This requirement relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference FR-MC-005.

Incoming Traceability should be derived dynamically from backlinks.

ConOps Relationship

FR-MC-005 establishes deployment to an Edge Environment without prescribing the edge platform, device class, provider, or connectivity model.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Requirement Status

Draft

Notes for Editors

This requirement page should retain the stable requirement identifier FR-MC-005.

The Statement should remain limited to deployment of identified deployment subjects to an Edge Environment.

Edge Deployment should not be treated as synonymous with disconnected or Air-Gapped Environment deployment.

Requirements for dependency capture, disconnected operation, synchronization, resource constraints, and network isolation should remain in their applicable requirement pages.

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

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-005#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.