MO-003d — Provider-Specific Dependency Limitation

Go to MO-003 — Cloud-Agnostic Deployment

Statement

Crucible SHALL confine dependencies on proprietary Cloud Provider interfaces, services, data formats, software development kits, and operational mechanisms to the applicable Provider Implementation.

Derived From

This requirement derives from:

The Original Requirement states:

The system SHALL provide cloud-agnostic deployment capabilities.[C3]

MO-003d preserves the portion of the Original Requirement that limits dependence on proprietary Cloud Provider mechanisms.

The separate requirements derived from MO-003 address:

Assessment

The Original Requirement uses the defined concept Cloud Agnosticism but does not identify:

The proprietary Cloud Provider dependencies subject to limitationThe Crucible components permitted to contain provider-specific dependenciesThe architectural boundary between provider-independent behavior and provider-specific behaviorThe mechanism used to isolate provider-specific dependenciesThe criteria used to detect provider-specific dependencies outside the permitted boundaryMO-003d:

Identifies proprietary Cloud Provider interfaces, services, data formats, software development kits, and operational mechanisms as the dependencies subject to limitationIdentifies the applicable Provider Implementation as the permitted location for those dependenciesEstablishes a defined boundary between provider-independent Crucible behavior and provider-specific implementation behaviorPrevents provider-specific dependencies from spreading into provider-independent Crucible componentsSeparates provider-specific dependency limitation from cross-platform deployment and common deployment-input requirements

Rationale

Cloud Agnosticism requires an architecture to limit dependence on the proprietary mechanisms of a particular Cloud Provider.

Provider-specific dependencies include:

Proprietary application programming interfacesProprietary servicesProprietary data formatsProvider-specific software development kitsProvider-specific command-line toolsProvider-specific authentication mechanismsProvider-specific resource identifiersProvider-specific configuration structuresProvider-specific deployment workflowsProvider-specific operational proceduresAllowing these dependencies within provider-independent Crucible components would couple the core architecture to one or more Cloud Providers.

The applicable Provider Implementation provides the controlled boundary within which provider-specific dependencies reside. The Provider Implementation translates provider-independent deployment intent into the proprietary mechanisms required by its target Cloud Provider or Deployment Platform.

Confining provider-specific dependencies supports:

Substitution of Provider ImplementationsAddition of new Deployment PlatformsReuse of provider-independent Crucible componentsControlled migration between Cloud ProvidersDetection of provider-specific implementation leakageReduced provider couplingConsistent Provider Contract enforcementIndependent testing of provider-specific behaviorThis requirement does not prohibit provider-specific dependencies. It limits those dependencies to the applicable Provider Implementation.

This requirement does not establish the Provider Contract requirements or the permitted Platform Specific Parameters. Lower-level functional and interoperability requirements establish those obligations.

Applies To

This requirement applies to:

Provider-independent Crucible componentsProprietary Cloud Provider interfacesProprietary Cloud Provider servicesProprietary Cloud Provider data formatsProvider-specific software development kitsProvider-specific operational mechanismsEvidenceProvenanceTraceability

Verification

Verification confirms that:

Each tested Cloud Provider or Deployment Platform has an identified Provider ImplementationEach Provider Implementation has a defined architectural boundaryProprietary Cloud Provider interfaces occur only within the applicable Provider ImplementationProprietary Cloud Provider services are accessed only through the applicable Provider ImplementationProprietary Cloud Provider data formats occur only within the applicable Provider Implementation or at its defined external boundaryProvider-specific software development kits are referenced only by the applicable Provider ImplementationProvider-specific operational mechanisms occur only within the applicable Provider ImplementationProvider-independent Crucible components do not contain dependencies on proprietary Cloud Provider mechanismsEach detected provider-specific dependency outside the permitted boundary is recorded as a findingThe generated Evidence supports the dependency-limitation determinationVerification includes:

Source-code dependency analysisBuild dependency analysisPackage dependency inspectionImport and module inspectionSoftware development kit reference inspectionApplication programming interface usage inspectionService endpoint inspectionData-format inspectionConfiguration inspectionCommand-line invocation inspectionRuntime dependency analysisNetwork interaction inspectionProvider Implementation boundary inspectionProvider Contract inspectionStatic analysisDynamic analysisCross-provider substitution testsFinding inspectionEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

Each tested Cloud Provider or Deployment PlatformThe applicable Provider ImplementationThe Provider Implementation boundaryThe applicable Provider ContractEach proprietary interface usedEach proprietary service usedEach proprietary data format usedEach provider-specific software development kit usedEach provider-specific operational mechanism usedThe Crucible component containing each identified dependencyEach provider-specific dependency detected outside the permitted boundaryThe result of each dependency analysisThe observed resultThe generated Evidence

Requirements Realized By

This requirement is realized by:

Related Architecture Sections

Referenced By

The following pages reference this requirement:

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification that proprietary Cloud Provider dependencies are confined to the applicable Provider Implementation.

Requirement Status

Draft

This requirement derives from MO-003 in the Crucible System Requirements Specification, Version 1.1 Draft.

Notes for Editors

This requirement page should retain the stable requirement identifier MO-003d.

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

Changes to the Statement SHALL preserve the provider-specific dependency-limitation intent derived from MO-003.

The architectural definition of each Provider Implementation boundary should identify:

The target Cloud Provider or Deployment PlatformThe applicable Provider ContractThe provider-independent interfaces exposed to CrucibleThe proprietary interfaces used by the Provider ImplementationThe proprietary services used by the Provider ImplementationThe proprietary data formats used by the Provider ImplementationThe provider-specific software development kits used by the Provider ImplementationThe provider-specific operational mechanisms used by the Provider ImplementationThe permitted external dependenciesThe prohibited dependencies outside the boundaryThe required EvidenceMaterial changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.

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-003d#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.