dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006d

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006d [2026/07/20 09:04] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006d [2026/07/30 05:29] (current) – [Delivery Phase] nick_dido
Line 1: Line 1:
-====== MO-006d — Lifecycle Transition Execution ======+====== MO-006d — Infrastructure Lifecycle Transition Execution ======
  
 [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|Go to MO-006 — Infrastructure Lifecycle Management]] [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|Go to MO-006 — Infrastructure Lifecycle Management]]
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL execute each [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] transition allocated to Crucible when the applicable transition conditions are satisfied.+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL execute each [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] transition allocated to Crucible when its transition conditions are satisfied.
  
 ===== Derived From ===== ===== Derived From =====
Line 21: Line 21:
 The separate requirements derived from MO-006 address: 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 Assignment]] +  * [[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 — Operational Lifecycle Initiation]] +  * [[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-006c|MO-006c — Current Lifecycle State Determination]]+  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006c|MO-006c — Infrastructure Lifecycle State Recording]]
   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006e|MO-006e — Infrastructure Environment Retirement]]   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006e|MO-006e — Infrastructure Environment Retirement]]
- 
-===== Assessment ===== 
- 
-The Original Requirement refers to infrastructure lifecycle management but does not identify the lifecycle-transition behavior performed by Crucible. 
- 
-Without an explicit lifecycle-transition requirement, an evaluator cannot reliably determine: 
- 
-  * Which transitions Crucible executes 
-  * Which transitions an external actor or system executes 
-  * The source state applicable to a transition 
-  * The target state applicable to a transition 
-  * The conditions that permit transition execution 
-  * The behavior required when transition conditions are not satisfied 
-  * The behavior required when transition execution fails 
-  * The Evidence required to demonstrate transition execution 
- 
-The phrase **lifecycle management** does not identify: 
- 
-  * The transition allocated to Crucible 
-  * The Infrastructure Environment subject to the transition 
-  * The current lifecycle state 
-  * The intended target lifecycle state 
-  * The applicable transition conditions 
-  * The transition result 
-  * The completion criteria 
-  * The failure criteria 
- 
-MO-006d: 
- 
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor 
-  * Limits the requirement to transitions allocated to Crucible 
-  * Requires satisfaction of the applicable transition conditions before execution 
-  * Separates transition execution from lifecycle assignment, lifecycle initiation, current-state determination, and Retirement 
-  * Avoids the ambiguous alternative **performs or coordinates** 
-  * Leaves transitions allocated to other actors or systems outside the scope of this requirement 
  
 ===== Rationale ===== ===== Rationale =====
  
-An Operational Lifecycle transition changes an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] from one lifecycle state to another lifecycle state. +An Operational Lifecycle transition changes an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] from one lifecycle state to another.
- +
-A lifecycle transition can include: +
- +
-  * Validation +
-  * Activation +
-  * Entry into operation +
-  * Entry into maintenance +
-  * Configuration change +
-  * Upgrade +
-  * Recovery +
-  * Restoration +
-  * Rollback +
-  * Compliance reassessment +
-  * Entry into Retirement Pending +
-  * Retirement+
  
-The assigned Operational Lifecycle defines:+An Operational Lifecycle revision defines:
  
   * The available lifecycle states   * The available lifecycle states
Line 91: Line 41:
   * The actor or system responsible for each transition   * The actor or system responsible for each transition
  
-Transition allocation prevents this requirement from implying that Crucible executes every transition in every Operational Lifecycle. An external operator, approval authority, orchestration service, security authority, or other system can remain responsible for transitions not allocated to Crucible.+Transition allocation prevents this requirement from implying that Crucible executes every transition in every Operational Lifecycle.
  
 Transition conditions can include: Transition conditions can include:
Line 107: Line 57:
   * Authorization by the responsible authority   * Authorization by the responsible authority
  
-Lifecycle Transition Execution supports:+Executing only allocated transitions after satisfaction of their transition conditions supports:
  
   * Controlled movement between lifecycle states   * Controlled movement between lifecycle states
Line 117: Line 67:
   * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]   * 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]]   * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * Generation of auditable [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] 
  
-Satisfaction of the transition conditions permits Crucible to execute the transition. Satisfaction of the transition conditions does not establish successful completion of the transition. The transition result determines whether the Infrastructure Environment enters the intended target state.+Satisfaction 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 successful entry into the intended target state. MO-006c governs determination of the current lifecycle state following transition execution.+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 assign the Operational Lifecycle. MO-006a establishes lifecycle assignment.+This requirement does not associate the Operational Lifecycle revision with the Infrastructure Environment. MO-006a addresses that association.
  
-This requirement does not establish the first lifecycle stage. MO-006b establishes lifecycle initiation.+This requirement does not initiate the Infrastructure Environment lifecycle. MO-006b addresses lifecycle initiation.
  
-This requirement does not determine the current lifecycle state. MO-006c establishes current lifecycle state determination. +This requirement does not retire the Infrastructure Environment. MO-006e addresses Retirement.
- +
-This requirement does not establish the specific Retirement transition. MO-006e establishes Infrastructure Environment Retirement.+
  
 ===== Applies To ===== ===== Applies To =====
Line 138: Line 85:
   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]]   * [[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]]   * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycles]]
 +  * Operational Lifecycle revisions
   * Operational Lifecycle states   * Operational Lifecycle states
   * Operational Lifecycle transitions   * Operational Lifecycle transitions
Line 148: Line 96:
   * Transition records   * Transition records
   * Infrastructure Baselines   * Infrastructure Baselines
-  * Infrastructure Deployment records 
-  * Configuration records 
   * Validation results   * Validation results
   * Security assessment results   * Security assessment results
Line 164: Line 110:
 Verification confirms that: Verification confirms that:
  
-  - The Infrastructure Environment is identified +  - The [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] is identified 
-  - The assigned Operational Lifecycle is identified+  - The associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] identifier and revision are identified
   - The current lifecycle state is identified   - The current lifecycle state is identified
   - The requested lifecycle transition is identified   - The requested lifecycle transition is identified
-  - The requested transition belongs to the assigned Operational Lifecycle +  - The requested transition belongs to the associated Operational Lifecycle revision 
-  - The requested transition is allocated to Crucible +  - The requested transition is allocated to [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] 
-  - The applicable transition conditions are identified +  - The transition conditions are identified 
-  - The applicable transition conditions are satisfied before execution begins+  - Each transition condition is satisfied before execution begins
   - Crucible executes the requested transition   - Crucible executes the requested transition
   - The transition produces an identified result   - The transition produces an identified result
-  - The transition result supports determination of the resulting lifecycle state +  - The transition result supports recording of the resulting lifecycle state 
-  - The transition record preserves the required Evidence, Provenance, and Traceability+  - A transition not allocated to Crucible is not executed by Crucible 
 +  - A transition with unsatisfied conditions is not executed 
 +  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Infrastructure Environment, Operational Lifecycle revision, source state, requested transition, transition allocation, condition evaluations, transition result, and resulting lifecycle state
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Environment inspection +The following pages reference this requirement:
-  * Operational Lifecycle assignment inspection +
-  * Current lifecycle-state inspection +
-  * Lifecycle-transition inspection +
-  * Transition-allocation inspection +
-  * Transition-condition inspection +
-  * Transition-request inspection +
-  * Valid-transition testing +
-  * Invalid-transition testing +
-  * Unsatisfied-condition testing +
-  * Transition-execution testing +
-  * Transition-completion testing +
-  * Transition-failure testing +
-  * Transition-result inspection +
-  * Resulting lifecycle-state inspection +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The Infrastructure Environment +===== Delivery Phase =====
-  - The assigned Operational Lifecycle +
-  - The Operational Lifecycle identifier +
-  - The Operational Lifecycle revision +
-  - The current lifecycle state +
-  - The requested lifecycle transition +
-  - The source lifecycle state +
-  - The intended target lifecycle state +
-  - The transition allocation +
-  - The applicable transition conditions +
-  - The result of each transition-condition evaluation +
-  - The transition start date and time +
-  - The transition completion date and time +
-  - The transition result +
-  - The resulting lifecycle-state determination +
-  - Each identified failure or exception +
-  - The observed result +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]+
  
-===== Requirements Realized By =====+Implemented and Verified.
  
-This requirement is realized by:+===== Implementation Status =====
  
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001|OR-001 — Operational Roles]] +<todo>Assess whether the current Crucible implementation executes each Operational Lifecycle transition allocated to Crucible when its transition conditions are satisfied.</todo>
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-002|OR-002 — Deployment Environments]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-004|OR-004 — Concurrent Environment Management]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-005|OR-005 — Distributed Environment Management]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|FR-CFG-001 through FR-CFG-005]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:start|FR-DEP-001 through FR-DEP-007]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-metadata-catalog-and-provenance:start|FR-MC-001 through FR-MC-005]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:start|FR-COMP-001 through FR-COMP-010]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:start|FR-DSO-001 through FR-DSO-006]]+
  
-===== Related Architecture Sections =====+===== Requirement Status =====
  
-  * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] +<todo>Review and accept MO-006d 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>
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] +
-  * [[dido:02-crusible:09-compliance-and-security:start|9. Compliance and Security]] +
-  * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]]+
  
-===== Referenced By =====+---- 
 +===== Issues =====
  
-The following pages reference this requirement:+The following unresolved issues affect this requirement:
  
-{{backlinks>.#dido:02-crusible}}+<todo>Define the Operational Lifecycle transitions allocated to Crucible.</todo>
  
-===== Delivery Phase =====+<todo>Define the source state, target state, and transition conditions for each transition allocated to Crucible.</todo>
  
-Phase 1 and subsequent phases+<todo>Define the completion and failure criteria for each transition allocated to Crucible.</todo>
  
-===== Implementation Status ===== +<todo>Define the behavior required when one or more transition conditions are not satisfied.</todo>
- +
-Not Assessed +
- +
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation executes each Operational Lifecycle transition allocated to Crucible when the applicable transition conditions are satisfied. +
- +
-===== Requirement Status =====+
  
-Draft+<todo>Define the behavior required when transition execution fails, is interrupted, or remains incomplete.</todo>
  
-This requirement derives from MO-006 in the Crucible System Requirements Specification, Version 1.1 Draft.+<todo>Define the recovery or rollback behavior associated with each transition allocated to Crucible.</todo>
  
 ---- ----
Line 269: Line 167:
 This page is a leaf requirement page and omits a trailing '':start'' from its namespace. This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Changes to the Statement should preserve execution of Operational Lifecycle transitions allocated to Crucible after satisfaction of the applicable transition conditions.+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 
 +  * An [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] transition as the executed behavior 
 +  * Allocation of the transition to Crucible 
 +  * Satisfaction of the transition conditions before execution 
 +  * An identified transition result
  
 The transition definition should identify: The transition definition should identify:
Line 279: Line 185:
   * The intended target lifecycle state   * The intended target lifecycle state
   * The actor or system allocated responsibility for the transition   * The actor or system allocated responsibility for the transition
-  * The applicable transition conditions+  * The transition conditions
   * The transition completion criteria   * The transition completion criteria
   * The transition failure criteria   * The transition failure criteria
-  * The applicable recovery or rollback behavior +  * The recovery or rollback behavior 
-  * The associated Provenance +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] 
-  * The associated Traceability +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * The supporting Evidence+
  
-Material changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.+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: To reference this requirement Statement from another wiki page, insert:
  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-006/mo-006d.1784563474.txt.gz
  • Last modified: 2026/07/20 09:04
  • by nick_dido