MO-006c — Infrastructure Lifecycle State Recording [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-006c — Infrastructure Lifecycle State Recording ======

[[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|Go to MO-006 — Infrastructure Lifecycle Management]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL record the current [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] state of each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].

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

This requirement derives from:

  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|MO-006 — Infrastructure Lifecycle Management]]

The Original Requirement states:

> //The system SHALL support infrastructure lifecycle management from initial deployment through retirement.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[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:

  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006a|MO-006a — Operational Lifecycle Association]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006b|MO-006b — Infrastructure Lifecycle Initiation]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006d|MO-006d — Infrastructure Lifecycle Transition Execution]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006e|MO-006e — Infrastructure Environment Retirement]]

===== Rationale =====

The current Operational Lifecycle state identifies the position of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] within its associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] revision.

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

  * Initial Deployment
  * Validation
  * Activation
  * Operational
  * Maintenance
  * Upgrade
  * Recovery
  * Restoration
  * Rollback
  * Compliance Reassessment
  * Retirement Pending
  * Retirement

An Infrastructure Environment does not necessarily use every state listed above.

Recording the current lifecycle state supports:

  * Selection of permitted lifecycle transitions
  * Evaluation of transition conditions
  * Prevention of invalid lifecycle transitions
  * Identification of incomplete or failed transitions
  * Coordination of lifecycle activities
  * Operational status reporting
  * Recovery and rollback decisions
  * Compliance and security evaluation
  * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

The recorded lifecycle state can be based on:

  * The associated Operational Lifecycle revision
  * The preceding lifecycle state
  * The most recent completed transition
  * The transition result
  * Observable Infrastructure Environment conditions
  * Infrastructure Deployment records
  * Configuration records
  * Validation results
  * Compliance results
  * Security results
  * Failure and exception records

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

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycles]]
  * Operational Lifecycle revisions
  * Operational Lifecycle states
  * Lifecycle-state criteria
  * Lifecycle-state records
  * Lifecycle associations
  * Lifecycle-initiation records
  * Lifecycle transitions
  * Transition conditions
  * Transition results
  * Infrastructure Deployment records
  * Configuration records
  * Validation results
  * Compliance results
  * Security results
  * Failure records
  * Exception records
  * [[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:

  - Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] is identified
  - The associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] identifier and revision are identified
  - The states defined by the associated Operational Lifecycle revision are identified
  - The criteria for each candidate lifecycle state are identified
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] records one current lifecycle state for each Infrastructure Environment
  - The recorded lifecycle state belongs to the associated Operational Lifecycle revision
  - The recorded lifecycle state agrees with the lifecycle records and observable Infrastructure Environment conditions
  - A failed or incomplete transition does not produce an unsupported target-state record
  - Conflicting or insufficient state information produces an identified result
  - The lifecycle-state record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|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:

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

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

Implemented and Verified.

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

<todo>Assess whether the current Crucible implementation records the current Operational Lifecycle state of each Infrastructure Environment.</todo>

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

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

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

The following unresolved issues affect this requirement:

<todo>Define the lifecycle states contained in each Operational Lifecycle revision.</todo>

<todo>Define the criteria used to assign each lifecycle state.</todo>

<todo>Define the source information Crucible uses to establish the current lifecycle state.</todo>

<todo>Define the behavior required when lifecycle records and observable Infrastructure Environment conditions conflict.</todo>

<todo>Define the state recorded after a failed, incomplete, interrupted, or rolled-back lifecycle transition.</todo>

<todo>Define when Crucible updates the current lifecycle-state record.</todo>

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

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor
  * Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] as the lifecycle subject
  * The current [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] state as the recorded information
  * The associated Operational Lifecycle revision as the source of permitted states

The lifecycle-state record should identify:

  * The Infrastructure Environment identifier
  * The Operational Lifecycle identifier
  * The Operational Lifecycle revision
  * The preceding lifecycle state
  * The most recent lifecycle transition
  * The transition result
  * The candidate lifecycle states
  * The state criteria
  * The observable Infrastructure Environment conditions
  * The recorded current lifecycle state
  * The recording date and time
  * The actor or process responsible for the record
  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

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-006:mo-006c#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>