MO-006a — Operational Lifecycle Assignment

Go to MO-006 — Infrastructure Lifecycle Management

Statement

Crucible SHALL associate each Infrastructure Environment with an identified Operational Lifecycle.

Derived From

This requirement derives from:

The Original Requirement states:

The system SHALL support infrastructure lifecycle management from initial deployment through retirement.[C1]

MO-006a preserves the lifecycle-management intent of the Original Requirement by requiring each Infrastructure Environment to have an identified Operational Lifecycle.

The separate requirements derived from MO-006 address:

Assessment

The Original Requirement refers to infrastructure lifecycle management but does not require an explicit relationship between an Infrastructure Environment and the Operational Lifecycle governing that environment.

Without an identified Operational Lifecycle, an evaluator cannot reliably determine:

Which lifecycle applies to the Infrastructure EnvironmentWhich lifecycle states applyWhich lifecycle transitions applyWhich lifecycle revision governs the environmentWhich transition conditions applyWhich Retirement conditions applyWhether the lifecycle differs from the lifecycle assigned to another Infrastructure EnvironmentThe phrase infrastructure lifecycle management does not identify:

The Infrastructure Environment governed by the lifecycleThe Operational Lifecycle assigned to the environmentThe identifier of the assigned lifecycleThe revision of the assigned lifecycleThe scope of the lifecycle assignmentThe Evidence required to demonstrate the assignmentMO-006a:

Identifies Crucible as the responsible actorIdentifies each Infrastructure Environment as the subject of the assignmentIdentifies an Operational Lifecycle as the assigned lifecycleRequires the Operational Lifecycle to be identifiedSeparates lifecycle assignment from lifecycle initiation, state determination, transition execution, and Retirement

Rationale

An identified Operational Lifecycle defines the lifecycle framework applicable to an Infrastructure Environment.

The lifecycle assignment provides the basis for determining:

The lifecycle states applicable to the Infrastructure EnvironmentThe permitted transitions between lifecycle statesThe conditions applicable to each transitionThe activities allocated to CrucibleThe activities allocated to external actors or systemsThe initial lifecycle stageThe terminal lifecycle stageThe applicable approval and control pointsThe Evidence associated with lifecycle activitiesDifferent Infrastructure Environments can require different Operational Lifecycles because of differences in:

Mission purposeOperational environmentSecurity classificationCompliance obligationsDeployment PlatformInfrastructure BaselineOrganizational policyOperational authorityMaintenance modelRetirement and disposition requirementsIdentifying the Operational Lifecycle supports:

Consistent lifecycle executionDetermination of the current lifecycle stateControlled lifecycle transitionsLifecycle-specific verificationReproducibility of lifecycle actionsPreservation of ProvenanceMaintenance of TraceabilityGeneration of auditable EvidenceThis requirement establishes the association between an Infrastructure Environment and an Operational Lifecycle.

This requirement does not initiate the assigned Operational Lifecycle. MO-006b establishes lifecycle initiation.

This requirement does not determine the current lifecycle state. MO-006c establishes current lifecycle state determination.

This requirement does not execute lifecycle transitions. MO-006d establishes lifecycle transition execution.

This requirement does not transition the Infrastructure Environment to Retirement. MO-006e establishes Infrastructure Environment Retirement.

Applies To

This requirement applies to:

Operational Lifecycle identifiersOperational Lifecycle revisionsLifecycle-assignment recordsLifecycle statesLifecycle transitionsTransition conditionsOperational environmentsDeployment PlatformsInfrastructure BaselinesSecurity profilesCompliance profilesOrganizational policiesOperational authoritiesEvidenceProvenanceTraceability

Verification

Verification confirms that:

The Infrastructure Environment is identifiedAn Operational Lifecycle is associated with the Infrastructure EnvironmentThe associated Operational Lifecycle has an identifierThe associated Operational Lifecycle revision is identifiableThe lifecycle assignment applies to the identified Infrastructure EnvironmentThe lifecycle assignment distinguishes the applicable Operational Lifecycle from other available lifecyclesThe assignment record preserves the required Evidence, Provenance, and TraceabilityVerification includes:

Infrastructure Environment inspectionOperational Lifecycle inspectionOperational Lifecycle identifier inspectionOperational Lifecycle revision inspectionLifecycle-assignment record inspectionCross-environment lifecycle-assignment comparisonLifecycle applicability inspectionEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

The Infrastructure EnvironmentThe assigned Operational LifecycleThe Operational Lifecycle identifierThe Operational Lifecycle revisionThe lifecycle-assignment recordThe effective assignment conditionThe authority or process responsible for the assignmentEach conflicting or missing lifecycle assignmentEach 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 associates each Infrastructure Environment with an identified Operational Lifecycle.

Requirement Status

Draft

This requirement derives from MO-006 in the Crucible System Requirements Specification, Version 1.1 Draft.

Notes for Editors

This requirement page should retain the stable requirement identifier MO-006a.

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

Changes to the Statement should preserve the association between each Infrastructure Environment and an identified Operational Lifecycle.

The lifecycle-assignment record should identify:

The Infrastructure Environment identifierThe Operational Lifecycle identifierThe Operational Lifecycle revisionThe effective assignment conditionThe assignment date and timeThe authority or process responsible for the assignmentThe applicable operational environmentThe applicable Deployment PlatformThe applicable security and compliance constraintsThe associated ProvenanceThe associated TraceabilityThe supporting 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-006:mo-006a#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.