MO-004d — External Resource Independence

Go to MO-004 — Connected and Disconnected Operations

Statement

Crucible SHALL execute each selected Operational Lifecycle activity in a Disconnected Environment without accessing an external resource outside the environment boundary.

Derived From

This requirement derives from:

The Original Requirement states:

The system SHALL support both connected and disconnected operational environments.[C1]

MO-004d preserves the implied requirement that Crucible operates within a Disconnected Environment without relying on external resources outside the environment boundary.

The separate requirements derived from MO-004 address:

Assessment

The Original Requirement does not identify the resource-availability constraint associated with operation in a Disconnected Environment.

The phrase support both connected and disconnected operational environments does not identify:

The boundary of the Disconnected EnvironmentThe external resources unavailable within that boundaryThe resources required by each selected Operational Lifecycle activityThe locally available replacements for external repositories, registries, services, and dependenciesThe behavior required when an external resource is unavailableThe treatment of attempted external accessThe Evidence required to demonstrate independence from external resourcesMO-004d:

Identifies Crucible as the responsible actorIdentifies execution of a selected Operational Lifecycle activity as the required behaviorIdentifies the Disconnected Environment boundary as the resource-availability boundaryProhibits access to external resources outside that boundary during executionSeparates resource availability from resource authorizationSeparates External Resource Independence from the general requirement to execute within a Disconnected Environment

Rationale

A Disconnected Environment does not provide continuous access to resources outside its defined boundary.

External resources can include:

External Artifact repositoriesExternal package repositoriesExternal image registriesPublic software repositoriesCloud-hosted application programming interfacesExternal identity servicesExternal licensing servicesExternal configuration servicesExternal time servicesExternal vulnerability feedsExternal documentation servicesExternal telemetry servicesExternal update servicesExternal name-resolution servicesExecution within a Disconnected Environment requires the necessary Controlled Inputs, dependencies, tools, repositories, registries, services, and other resources to exist within the environment boundary before execution begins.

Required resources can enter the Disconnected Environment through an approved transfer and admission process. After successful transfer, authorization, integrity verification, and admission, the resources become available within the environment boundary and no longer constitute external resources for the applicable execution.

External Resource Independence supports:

Predictable execution without external connectivityOperation during network outagesOperation within restricted network boundariesOperation in Air-Gapped EnvironmentsControlled dependency captureComplete offline transfer preparationReproducible executionPrevention of hidden external dependenciesEvidence of disconnected operationThis requirement addresses resource availability. MO-004c separately prohibits access to resources that lack authorization for the applicable operational environment.

A resource can be available within the environment but unauthorized. A resource can also be authorized for use but unavailable within the environment. The two conditions require separate evaluation.

Applies To

This requirement applies to:

Environment boundariesExternal resourcesLocal resourcesOperational Lifecycle activitiesControlled InputsAuthorized ResourcesArtifactsTransfer BundlesImported dependenciesLocal Artifact repositoriesLocal package repositoriesLocal image registriesLocal network servicesCI/CD PipelinesInfrastructure DeploymentsProvisioningCompliance AssessmentsDeployment ValidationEvidenceProvenanceTraceability

Verification

Verification confirms that:

The applicable Disconnected Environment boundary is identifiedThe selected Operational Lifecycle activity is identifiedThe resources required by the selected activity are identifiedEach required resource is available within the Disconnected Environment boundaryExternal network connectivity is unavailable during executionCrucible executes the selected activity without accessing an external resource outside the environment boundaryEach attempted external resource access is detected and recordedThe selected activity reaches its defined completion conditionThe selected activity produces its required outputsThe execution record preserves the required Evidence, Provenance, and TraceabilityVerification includes:

Disconnected Environment boundary inspectionOperational Lifecycle activity inspectionRequired-resource inventory inspectionLocal repository inspectionLocal registry inspectionLocal service inspectionTransfer Bundle inspectionImported dependency inspectionNetwork-disconnection testsNetwork-traffic inspectionDomain-name resolution inspectionExternal-endpoint access testingHidden-dependency testingOperational Lifecycle execution testsCompletion-condition inspectionOutput inspectionAudit-record inspectionEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

The Disconnected EnvironmentThe environment boundaryThe selected Operational Lifecycle activityThe applicable activity identifier and revisionThe resources required by the selected activityThe resources available within the environment boundaryThe imported Artifacts and dependenciesThe local repositories, registries, and services used during executionThe network-disconnection conditionEach attempted access to an external resourceThe result of each attempted external accessThe applicable starting conditionThe applicable completion conditionThe execution resultThe outputs producedEach identified hidden or unresolved external dependencyThe 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 the current Crucible implementation executes selected Operational Lifecycle activities in a Disconnected Environment without accessing external resources outside the environment boundary.

Requirement Status

Draft

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

Notes for Editors

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

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

Changes to the Statement SHALL preserve the External Resource Independence intent derived from MO-004.

The applicable Disconnected Environment definition should identify:

The environment boundaryThe permitted internal networksThe unavailable external networksThe local repositoriesThe local registriesThe local servicesThe required Controlled InputsThe imported Artifacts and dependenciesThe applicable transfer and admission processesThe required monitoring and audit recordsThe 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-004:mo-004d#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.