MO-004a — Connected Environment Operations [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== MO-004a — Connected Environment Operations ======

[[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:start|Go to MO-004 — Connected and Disconnected Operations]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL execute each selected [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activity in a [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]].

===== Derived From =====

This requirement derives from:

  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:start|MO-004 — Connected and Disconnected Operations]]

The Original Requirement states:

> //The system SHALL support both connected and disconnected operational environments.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

MO-004a preserves the portion of the Original Requirement that requires [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] to operate within a [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]].

The separate requirements derived from MO-004 address:

  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004b|MO-004b — Disconnected Environment Operations]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004c|MO-004c — Authorized Resource Use]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004d|MO-004d — Disconnected Resource Availability]]

===== Rationale =====

A [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] provides network connectivity to resources required by selected Operational Lifecycle activities.

Operational Lifecycle activities can include:

  * Artifact acquisition
  * Dependency resolution
  * Baseline composition
  * Machine Image construction
  * Infrastructure Deployment
  * Provisioning
  * Configuration
  * Compliance Assessment
  * Security assessment
  * Deployment Validation
  * Evidence generation
  * Artifact promotion
  * Operational maintenance

The 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:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]]
  * Selected Operational Lifecycle activities
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:authorized_resource|Authorized Resources]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]
  * Artifact repositories
  * Package repositories
  * Image registries
  * Authorized network services
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_assessment|Compliance Assessments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

===== Verification =====

Verification confirms that:

  - The [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] is identified
  - Each selected [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activity is identified
  - The inputs required by each selected activity are identified
  - The resources used by each selected activity are identified
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes each selected activity within the Connected Environment
  - Each selected activity reaches its defined completion condition
  - Each selected activity produces its required outputs
  - Each failure or exception is identified
  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Connected Environment, selected activity, Controlled Inputs, resources used, execution result, and outputs produced

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:02-crusible}}

===== Delivery Phase =====

Implemented and Verified

===== Implementation Status =====

<todo>Assess whether the current Crucible implementation executes each selected Operational Lifecycle activity in a Connected Environment.</todo>

===== Requirement Status =====

<todo>Review and accept MO-004a as a proposed derived requirement created from the evaluation and decomposition of MO-004 in the Crucible System Requirements Specification, Version 1.1 Draft.</todo>

----
===== Issues =====

The following unresolved issues affect this requirement:

<todo>Identify the Operational Lifecycle activities that Crucible must execute within a Connected Environment.</todo>

<todo>Identify the controlling source that selects the Operational Lifecycle activities for a Connected Environment.</todo>

<todo>Define the starting condition, completion condition, required inputs, required outputs, and failure criteria for each selected Operational Lifecycle activity.</todo>

<todo>Identify the resources available within each Connected Environment and distinguish available resources from Authorized Resources.</todo>

----
===== 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:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor
  * The selected [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activity as the required behavior
  * The [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] as the operational context
  * Execution of each selected activity as the required outcome

The 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:

<code dokuwiki>
{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004a#Statement&noheader&nofooter&noeditbtn}}
</code>

Do not rename this page after an external citation unless a redirect or move plan is in place.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>