MO-004a — Connected Environment Operations

Go to MO-004 — Connected and Disconnected Operations

Statement

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

Derived From

This requirement derives from:

The Original Requirement states:

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

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

The separate requirements derived from MO-004 address:

Rationale

A Connected Environment provides network connectivity to resources required by selected Operational Lifecycle activities.

Operational Lifecycle activities can include:

Artifact acquisitionDependency resolutionBaseline compositionMachine Image constructionInfrastructure DeploymentProvisioningConfigurationCompliance AssessmentSecurity assessmentDeployment ValidationEvidence generationArtifact promotionOperational maintenanceThe selected activities define the required scope of execution. Selection prevents this requirement from implying that every Operational Lifecycle activity applies to every Connected Environment or operational context.

Execution in a Connected Environment supports access to network services, repositories, registries, data sources, and other resources available within the environment.

This requirement does not establish the requirements for execution in a Disconnected Environment. MO-004b addresses that outcome.

This requirement does not establish which resources Crucible is authorized to use. MO-004c addresses Authorized Resource use.

Applies To

This requirement applies to:

Selected Operational Lifecycle activitiesControlled InputsAuthorized ResourcesArtifactsArtifact repositoriesPackage repositoriesImage registriesAuthorized network servicesCI/CD PipelinesInfrastructure DeploymentsProvisioningCompliance AssessmentsDeployment ValidationEvidenceProvenanceTraceability

Verification

Verification confirms that:

The Connected Environment is identifiedEach selected Operational Lifecycle activity is identifiedThe inputs required by each selected activity are identifiedThe resources used by each selected activity are identifiedCrucible executes each selected activity within the Connected EnvironmentEach selected activity reaches its defined completion conditionEach selected activity produces its required outputsEach failure or exception is identifiedThe verification record preserves Traceability among the Connected Environment, selected activity, Controlled Inputs, resources used, execution result, and outputs produced

Referenced By

The following pages reference this requirement:

Delivery Phase

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

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 Connected Environment as the operational contextExecution of each selected activity as the required outcomeThe unresolved activity-selection source should remain recorded in the Issues section until a controlling source identifies the activities required within a Connected Environment.

Material 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-004a#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.