MO-004d — Disconnected Resource Availability

Go to MO-004 — Connected and Disconnected Operations

Statement

Crucible SHALL execute each selected Operational Lifecycle activity in a Disconnected Environment using only the required resources available within 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 portion of the Original Requirement that requires the resources needed for disconnected operation to be available within the Disconnected Environment boundary.

The separate requirements derived from MO-004 address:

Rationale

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

Each selected Operational Lifecycle activity therefore requires its inputs, dependencies, tools, repositories, registries, services, and other resources to be available within the environment boundary before execution.

Required resources can include:

ArtifactsSoftware packagesMachine ImagesArtifact repositoriesPackage repositoriesImage registriesConfiguration dataSecurity and compliance contentIdentity and authorization informationLicensing informationName-resolution servicesTime servicesBuild and deployment toolsEvidence-generation toolsResources imported through an approved transfer process become available within the Disconnected Environment only after the required transfer, authorization, integrity, provenance, and admission checks succeed.

Ensuring resource availability within the environment boundary supports:

Execution without continuous external connectivityOperation during network outagesOperation within restricted network boundariesOperation in Air-Gapped EnvironmentsDetection of hidden external dependenciesControlled dependency captureComplete offline transfer preparationReproducible executionGeneration of Evidence for disconnected operationThis requirement addresses resource availability. MO-004c separately requires Crucible to use only Authorized Resources.

A resource can be available within the environment but not authorized for use. A resource can also be authorized for use but unavailable within the environment.

Applies To

This requirement applies to:

Environment boundariesRequired resourcesExternal resourcesLocal resourcesOperational Lifecycle activitiesControlled InputsAuthorized ResourcesArtifactsTransfer BundlesImported dependenciesLocal Artifact repositoriesLocal package repositoriesLocal image registriesLocal servicesEvidenceProvenanceTraceability

Verification

Verification confirms that:

The Disconnected Environment boundary is identifiedEach selected Operational Lifecycle activity is identifiedThe resources required by each selected activity are identifiedEach required resource is available within the Disconnected Environment boundary before executionEach imported resource has completed the required transfer, authorization, integrity, provenance, and admission checksCrucible executes each selected activity using only resources available within the environment boundaryEach selected activity executes without access to an external resource outside the environment boundaryEach attempted access to an external resource is detected and recordedEach selected activity reaches its defined completion conditionEach selected activity produces its required outputsThe verification record preserves Traceability among the Disconnected Environment, selected activity, required resources, available resources, execution result, and outputs produced

Referenced By

The following pages reference this requirement:

Delivery Phase

Implemented and Verified.

Implementation Status

Requirement Status

Issues

The following unresolved issues affect this requirement:

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.

The parent MO-004 page is a non-leaf page and retains a trailing :start in its namespace.

Changes to the Statement should preserve:

as the responsible actorThe selected Operational Lifecycle activity as the required behaviorThe Disconnected Environment boundary as the resource-availability boundaryAvailability of all required resources within the environment boundaryExecution without access to external resources outside the environment boundaryThe definition of each Disconnected Environment should identify:

The environment boundaryThe permitted internal networksThe unavailable external networksThe local repositoriesThe local registriesThe local servicesThe required Controlled InputsThe imported Artifacts and dependenciesThe transfer and admission processesThe monitoring and audit recordsMaterial changes should receive review and should update the verification criteria, source records, and Issues section.

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.