MO-004b — Disconnected Environment Operation

Go to MO-004 — Connected and Disconnected Operations

Statement

Crucible SHALL execute each selected Operational Lifecycle activity in a Disconnected Environment.

Derived From

This requirement derives from:

The Original Requirement states:

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

MO-004b preserves the portion of the Original Requirement that requires Crucible to operate within a Disconnected Environment.

The separate requirements derived from MO-004 address:

Assessment

The Original Requirement uses support without identifying the behavior Crucible performs.

The phrase disconnected operational environments does not identify:

The Operational Lifecycle activities performedThe method used to select those activitiesThe inputs required by each activityThe outputs produced by each activityThe resources available within the Disconnected EnvironmentThe completion conditions applicable to each activityThe treatment of unavailable external resourcesThe Evidence required to demonstrate successful executionMO-004b:

Replaces support with the direct action executeIdentifies Crucible as the responsible actorIdentifies the selected Operational Lifecycle activity as the required behaviorIdentifies a Disconnected Environment as the applicable operational contextSeparates Disconnected Environment operation from Connected Environment operationSeparates execution behavior from resource authorization and external-resource independence

Rationale

A Disconnected Environment does not provide continuous access to resources outside the environment boundary.

Operational Lifecycle activities can include:

Artifact acquisition from resources already present within the environmentDependency resolution from local repositoriesBaseline compositionMachine Image constructionInfrastructure DeploymentProvisioningConfigurationCompliance AssessmentSecurity assessmentDeployment ValidationEvidence generationArtifact promotion within the environmentOperational maintenanceThe selected activities define the scope of the required execution. Selection prevents the requirement from implying that every Operational Lifecycle activity applies to every Disconnected Environment or deployment scenario.

Execution in a Disconnected Environment depends on the prior availability of the Controlled Inputs, dependencies, repositories, tools, and other Authorized Resources required by the selected activity.

Resources imported through an approved transfer process become available for use only after the applicable authorization, integrity, provenance, and admission checks succeed.

Disconnected Environment operation supports:

Controlled operation without continuous external connectivityUse of locally available repositories and registriesUse of transferred Artifacts and dependenciesReproducible executionEvidence generationPreservation of ProvenanceMaintenance of TraceabilityOperation within security and information-boundary constraintsThis requirement does not establish the requirements for operation in a Connected Environment. MO-004a establishes those requirements.

This requirement does not permit access to unauthorized resources. MO-004c establishes the applicable prohibition.

This requirement does not establish independence from unavailable external resources. MO-004d establishes that requirement.

Applies To

This requirement applies to:

Operational Lifecycle activitiesControlled InputsAuthorized ResourcesArtifactsLocal Artifact repositoriesLocal package repositoriesLocal image registriesTransfer BundlesImported dependenciesCI/CD PipelinesInfrastructure DeploymentsProvisioningCompliance AssessmentsDeployment ValidationEvidenceProvenanceTraceability

Verification

Verification confirms that:

The Disconnected Environment is identifiedThe selected Operational Lifecycle activity is identifiedThe inputs required by the selected activity are identifiedThe Authorized Resources available within the Disconnected Environment are identifiedCrucible executes the selected activity within the Disconnected EnvironmentThe selected activity reaches its defined completion conditionThe selected activity produces its required outputsThe execution does not depend on continuous external connectivityThe execution record preserves the required Evidence, Provenance, and TraceabilityVerification includes:

Disconnected Environment inspectionOperational Lifecycle activity inspectionControlled Input inspectionAuthorized Resource inspectionLocal repository-access testsLocal registry-access testsTransfer Bundle inspectionImported dependency inspectionNetwork-disconnection testsCI/CD Pipeline tests within the Disconnected EnvironmentOperational Lifecycle execution testsCompletion-condition inspectionOutput inspectionEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

The Disconnected EnvironmentThe selected Operational Lifecycle activityThe applicable activity identifier and revisionThe selected Controlled InputsThe Authorized Resources used during executionThe imported Artifacts and dependencies used during executionThe applicable starting conditionThe applicable completion conditionThe execution resultThe outputs producedEach identified failure or exceptionThe 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 the selected Operational Lifecycle activity in a Disconnected Environment.

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-004b.

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

Changes to the Statement SHALL preserve the Disconnected Environment operation intent derived from MO-004.

The selected Operational Lifecycle activity should identify:

The activity identifierThe activity revisionThe applicable Disconnected EnvironmentThe required Controlled InputsThe Authorized Resources available within the environmentThe imported Artifacts and dependencies required by the activityThe starting conditionThe completion conditionThe required outputsThe applicable failure criteriaThe 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-004b#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.