MO-006c — Infrastructure Lifecycle State Recording

Go to MO-006 — Infrastructure Lifecycle Management

Statement

Crucible SHALL record the current Operational Lifecycle state of each Infrastructure Environment.

Derived From

This requirement derives from:

The Original Requirement states:

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

MO-006c preserves the lifecycle-management intent of the Original Requirement by requiring Crucible to record the current Operational Lifecycle state of each Infrastructure Environment.

The separate requirements derived from MO-006 address:

Rationale

The current Operational Lifecycle state identifies the position of an Infrastructure Environment within its associated Operational Lifecycle revision.

The associated Operational Lifecycle revision defines the permitted states. Those states can include:

Initial DeploymentValidationActivationOperationalMaintenanceUpgradeRecoveryRestorationRollbackCompliance ReassessmentRetirement PendingRetirementAn Infrastructure Environment does not necessarily use every state listed above.

Recording the current lifecycle state supports:

Selection of permitted lifecycle transitionsEvaluation of transition conditionsPrevention of invalid lifecycle transitionsIdentification of incomplete or failed transitionsCoordination of lifecycle activitiesOperational status reportingRecovery and rollback decisionsCompliance and security evaluationPreservation of ProvenanceMaintenance of TraceabilityThe recorded lifecycle state can be based on:

The associated Operational Lifecycle revisionThe preceding lifecycle stateThe most recent completed transitionThe transition resultObservable Infrastructure Environment conditionsInfrastructure Deployment recordsConfiguration recordsValidation resultsCompliance resultsSecurity resultsFailure and exception recordsA failed or incomplete transition does not establish successful entry into its intended target state.

This requirement records the current lifecycle state. It does not execute a lifecycle transition. MO-006d addresses lifecycle transition execution.

This requirement does not associate or initiate the Operational Lifecycle. MO-006a and MO-006b address those outcomes.

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

Applies To

This requirement applies to:

Operational Lifecycle revisionsOperational Lifecycle statesLifecycle-state criteriaLifecycle-state recordsLifecycle associationsLifecycle-initiation recordsLifecycle transitionsTransition conditionsTransition resultsInfrastructure Deployment recordsConfiguration recordsValidation resultsCompliance resultsSecurity resultsFailure recordsException recordsEvidenceProvenanceTraceability

Verification

Verification confirms that:

Each Infrastructure Environment is identifiedThe associated Operational Lifecycle identifier and revision are identifiedThe states defined by the associated Operational Lifecycle revision are identifiedThe criteria for each candidate lifecycle state are identifiedCrucible records one current lifecycle state for each Infrastructure EnvironmentThe recorded lifecycle state belongs to the associated Operational Lifecycle revisionThe recorded lifecycle state agrees with the lifecycle records and observable Infrastructure Environment conditionsA failed or incomplete transition does not produce an unsupported target-state recordConflicting or insufficient state information produces an identified resultThe lifecycle-state record preserves Traceability among the Infrastructure Environment, Operational Lifecycle revision, preceding state, transition result, observed conditions, and recorded current state

Referenced By

The following pages reference this requirement:

Delivery Phase

Implemented and Verified.

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

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 actorEach Infrastructure Environment as the lifecycle subjectThe current Operational Lifecycle state as the recorded informationThe associated Operational Lifecycle revision as the source of permitted statesThe lifecycle-state record should identify:

The Infrastructure Environment identifierThe Operational Lifecycle identifierThe Operational Lifecycle revisionThe preceding lifecycle stateThe most recent lifecycle transitionThe transition resultThe candidate lifecycle statesThe state criteriaThe observable Infrastructure Environment conditionsThe recorded current lifecycle stateThe recording date and timeThe actor or process responsible for the recordThe 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-006c#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.