MO-004

Go to C.1 Mission Objectives

Statement

Crucible SHALL execute the applicable Operational Lifecycle activities in both Connected Environments and Disconnected Environments using only the resources authorized and available within each environment.

Source Statement

The system SHALL support both connected and disconnected operational environments.

Source

Crucible System Requirements Specification, Version 1.1 Draft, Mission Objectives, MO-004.

Assessment

The source statement expresses the approved mission objective but does not provide a fully testable formulation.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system nameSupport is a weak verb that does not identify the behavior Crucible performsOperational environments does not identify the environmental characteristics, available resources, access restrictions, or applicable activitiesThe source statement does not identify which Operational Lifecycle activities must operate in each environmentThe source statement does not identify whether a Disconnected Environment may obtain required resources through an approved transfer processThe source statement does not define how verification distinguishes a connected workflow from a disconnected workflowThe normalized Statement replaces the weak verb with execute, identifies the applicable environments, and constrains execution to the resources authorized and available within each environment.

Rationale

Organizations may construct, deploy, maintain, and validate infrastructure in environments with different network access conditions.

A Connected Environment may access approved external repositories, services, and providers during execution.

A Disconnected Environment cannot depend on unavailable external network services during execution. An Air-Gapped Environment imposes additional physical or logical separation requirements.

Crucible addresses these conditions by coordinating:

Reusable BaselinesBaseline CompositionImage LayersInfrastructure BaselinesMachine Image constructionDependency captureOffline transferInfrastructure DeploymentProvisioningCompliance assessmentEvidence generationThe connected workflow captures the dependencies, artifacts, and Compliance Findings required by the disconnected workflow.

An approved transfer process moves the resulting transfer bundle into the target Disconnected Environment.

Applies To

This requirement applies to:

constructionDependency captureDependency storesTransfer bundlesOffline transferInfrastructure DeploymentProvisioningCompliance assessmentCompliance FindingsEvidenceConnected EnvironmentsDisconnected EnvironmentsAir-Gapped EnvironmentsCI/CD PipelinesOperational Lifecycle

Verification

Verification SHALL confirm that Crucible executes the applicable Operational Lifecycle activities in a Connected EnvironmentVerification SHALL confirm that Crucible executes the applicable Operational Lifecycle activities in a Disconnected EnvironmentVerification SHALL confirm that the disconnected workflow does not require access to external network resources that are unavailable within the target environmentVerification SHALL confirm that the connected workflow captures the dependencies required by the disconnected workflowVerification SHALL confirm that the connected workflow produces a transferable bundle containing the required dependencies, artifacts, provenance information, and Compliance FindingsVerification SHALL confirm that the approved transfer process preserves the integrity of the transfer bundleVerification SHALL confirm that the target Disconnected Environment imports and validates the transfer bundleVerification SHALL confirm that the disconnected workflow uses only resources authorized and available within the target environmentVerification SHALL confirm that equivalent controlled inputs produce results that satisfy the applicable acceptance criteria in both environmentsVerification SHALL confirm that the workflow records the differences between connected and disconnected execution conditionsVerification SHALL confirm that deployment and Evidence records preserve Traceability across the transfer boundaryVerification may include:

Connected build testsDisconnected build testsDependency capture testsDependency store inspectionTransfer bundle export testsTransfer bundle integrity testsTransfer bundle import testsOffline package repository testsOffline provider repository testsMachine Image build testsInfrastructure Deployment testsCompliance assessment testsEvidence generation testsNetwork isolation testsAir-Gapped Environment demonstrationsEnd-to-end CI/CD Pipeline testsThe verification record SHALL identify:

The tested Crucible DescriptionThe tested BaselinesThe applicable Operational Lifecycle activitiesThe connected execution conditionsThe disconnected execution conditionsThe authorized external resourcesThe prohibited external resourcesThe captured dependenciesThe dependency storeThe transfer bundleThe bundle integrity verification resultThe transfer authorizationThe imported resourcesThe controlled inputsThe applicable acceptance criteriaThe observed resultsThe generated Evidence

Outgoing Traceability

This requirement is realized by:

This requirement also relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference `MO-004`.

Incoming traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship.

ConOps Relationship

The Crucible Concept of Operations describes a connected to disconnected supply chain.

In a Connected Environment, Crucible:

Resolves required dependenciesBuilds and hardens Machine ImagesCaptures operating system packages and installation mediaCaptures Compliance FindingsProduces a transfer bundleIn a Disconnected Environment, Crucible:

Imports the transfer bundleValidates the transferred contentPopulates internal dependency repositoriesPerforms offline builds and updatesPerforms Infrastructure DeploymentPreserves artifact provenance and TraceabilityThe ConOps identifies dependency capture, compressed bundle transfer, and enclave repository population as the operational realization of disconnected execution.

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification of the applicable Operational Lifecycle activities in both a Connected Environment and a Disconnected Environment.

Requirement Status

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.

Notes for Editors

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

Changes to the Statement SHALL preserve the approved intent of the source requirement.

Material changes should receive review and should update the related outbound traceability, verification criteria, acceptance criteria, and source records.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.

The shared Terms and Definitions corpus should include definitions for:

Authorized ResourceDependency CaptureDependency StoreDisconnected ExecutionEnclaveNetwork IsolationOffline RepositoryOffline TransferOperational EnvironmentTransfer AuthorizationTransfer BoundaryTransfer BundleTransfer Bundle IntegrityThe proposed namespaces are:

`dido:99_annexes:annex-b-terms-and-definitions:a:authorized_resource``dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture``dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store``dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_execution``dido:99_annexes:annex-b-terms-and-definitions:e:enclave``dido:99_annexes:annex-b-terms-and-definitions:n:network_isolation``dido:99_annexes:annex-b-terms-and-definitions:o:offline_repository``dido:99_annexes:annex-b-terms-and-definitions:o:offline_transfer``dido:99_annexes:annex-b-terms-and-definitions:o:operational_environment``dido:99_annexes:annex-b-terms-and-definitions:t:transfer_authorization``dido:99_annexes:annex-b-terms-and-definitions:t:transfer_boundary``dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle``dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle_integrity`Do not rename this page once it has been cited externally unless a redirect or move plan is in place.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.