MO-006d — Infrastructure Lifecycle Transition Execution

Go to MO-006 — Infrastructure Lifecycle Management

Statement

Crucible SHALL execute each Operational Lifecycle transition allocated to Crucible when its transition conditions are satisfied.

Derived From

This requirement derives from:

The Original Requirement states:

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

MO-006d preserves the lifecycle-management intent of the Original Requirement by requiring Crucible to execute the Operational Lifecycle transitions allocated to it.

The separate requirements derived from MO-006 address:

Rationale

An Operational Lifecycle transition changes an Infrastructure Environment from one lifecycle state to another.

An Operational Lifecycle revision defines:

The available lifecycle statesThe permitted transitionsThe source state for each transitionThe target state for each transitionThe transition conditionsThe transition completion criteriaThe transition failure criteriaThe actor or system responsible for each transitionTransition allocation prevents this requirement from implying that Crucible executes every transition in every Operational Lifecycle.

Transition conditions can include:

Current lifecycle stateApproval statusInfrastructure Environment statusInfrastructure Baseline statusValidation resultsSecurity assessment resultsCompliance assessment resultsAvailability of required resourcesCompletion of preceding activitiesAbsence of unresolved blocking failuresAuthorization by the responsible authorityExecuting only allocated transitions after satisfaction of their transition conditions supports:

Controlled movement between lifecycle statesPrevention of invalid transitionsConsistent enforcement of transition conditionsIdentification of transition completionIdentification of transition failureRecovery from failed transitionsPreservation of ProvenanceMaintenance of TraceabilitySatisfaction of the transition conditions permits execution of the transition. Satisfaction of the transition conditions does not establish successful completion.

A failed or incomplete transition does not establish entry into the intended target state. MO-006c addresses recording of the current lifecycle state after transition execution.

This requirement does not associate the Operational Lifecycle revision with the Infrastructure Environment. MO-006a addresses that association.

This requirement does not initiate the Infrastructure Environment lifecycle. MO-006b addresses lifecycle initiation.

This requirement does not retire the Infrastructure Environment. MO-006e addresses Retirement.

Applies To

This requirement applies to:

Operational Lifecycle revisionsOperational Lifecycle statesOperational Lifecycle transitionsTransition allocationsTransition conditionsTransition completion criteriaTransition failure criteriaTransition requestsTransition resultsTransition recordsInfrastructure BaselinesValidation resultsSecurity assessment resultsCompliance assessment resultsApproval recordsFailure recordsException recordsEvidenceProvenanceTraceability

Verification

Verification confirms that:

The Infrastructure Environment is identifiedThe associated Operational Lifecycle identifier and revision are identifiedThe current lifecycle state is identifiedThe requested lifecycle transition is identifiedThe requested transition belongs to the associated Operational Lifecycle revisionThe requested transition is allocated to CrucibleThe transition conditions are identifiedEach transition condition is satisfied before execution beginsCrucible executes the requested transitionThe transition produces an identified resultThe transition result supports recording of the resulting lifecycle stateA transition not allocated to Crucible is not executed by CrucibleA transition with unsatisfied conditions is not executedThe verification record preserves Traceability among the Infrastructure Environment, Operational Lifecycle revision, source state, requested transition, transition allocation, condition evaluations, transition result, and resulting lifecycle state

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-006d.

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

The parent MO-006 page is a non-leaf page and retains a trailing :start in its namespace.

Changes to the Statement should preserve:

as the responsible actorAn Operational Lifecycle transition as the executed behaviorAllocation of the transition to CrucibleSatisfaction of the transition conditions before executionAn identified transition resultThe transition definition should identify:

The Operational Lifecycle identifierThe Operational Lifecycle revisionThe transition identifierThe source lifecycle stateThe intended target lifecycle stateThe actor or system allocated responsibility for the transitionThe transition conditionsThe transition completion criteriaThe transition failure criteriaThe recovery or rollback behaviorThe associated ProvenanceThe associated TraceabilityMaterial 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-006:mo-006d#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.