Differences

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

--- dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start [2026/07/20 09:10] – nick_dido
+++ dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start [2026/07/22 12:32] (current) – nick_dido
@@ Line 14: / Line 14: @@
   * **The system** does not use the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
-  * **Support** is a weak verb that does not identify the behavior Crucible performs
+  * **Support** is a weak verb that does not identify an observable behavior performed by Crucible
   * **Infrastructure** does not identify the lifecycle subject as an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]]
-  * **Infrastructure lifecycle management** combines multiple independently verifiable behaviors
+  * **Infrastructure lifecycle management** combines multiple independently testable behaviors
-  * The Original Requirement does not require association of an Infrastructure Environment with an identified [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]]
+  * **Initial deployment** introduces a separate lifecycle-initiation obligation
-  * The Original Requirement does not identify the Operational Lifecycle revision applicable to the Infrastructure Environment
+  * **Through retirement** introduces a separate terminal lifecycle obligation
-  * **Initial deployment** embeds a separate lifecycle-initiation obligation
-  * **Through retirement** embeds a separate terminal lifecycle obligation
-  * The Original Requirement does not identify the current lifecycle state of the Infrastructure Environment
-  * The Original Requirement does not identify the lifecycle transitions allocated to Crucible
-  * The Original Requirement does not identify the conditions that permit a lifecycle transition
-  * The Original Requirement does not identify the conditions that permit [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]]
-  * The Original Requirement combines lifecycle assignment, lifecycle initiation, lifecycle-state determination, lifecycle-transition execution, and Retirement within one normative statement
-  * These obligations can pass or fail independently
-  * The Original Requirement does not provide independently identifiable statements for verification and traceability
-The previously normalized Statement also combined:
+The Original Requirement does not identify:
-  * Management of each Infrastructure Environment
+  * The [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] associated with each Infrastructure Environment
-  * Association with an applicable Operational Lifecycle
+  * The Operational Lifecycle revision associated with each Infrastructure Environment
-  * Lifecycle initiation at the initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]]
+  * The lifecycle state assigned when the Infrastructure Environment is created
-  * Management of intermediate lifecycle states
+  * The current lifecycle state of the Infrastructure Environment
-  * Execution or coordination of lifecycle transitions
+  * The lifecycle transitions that Crucible performs
-  * Continuation of lifecycle management through Retirement
+  * The conditions that permit each lifecycle transition
+  * The conditions that permit [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]]
+  * The lifecycle records preserved for verification and Traceability
-These obligations can pass or fail independently. The term **throughout** also does not identify whether the requirement applies continuously, during each lifecycle state, during each transition, or whenever a lifecycle activity occurs. The current page consequently places several substantive obligations within its Verification section rather than expressing them as atomic Statements. :contentReference[oaicite:0]{index=0}
+The Original Requirement therefore requires:
-The Original Requirement therefore requires decomposition into independently identifiable normative requirements.
+  * Replacement of **the system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
+  * Replacement of **support** with observable Crucible behavior
+  * Identification of the lifecycle subject as an Infrastructure Environment
+  * Association of each Infrastructure Environment with an identified Operational Lifecycle revision
+  * Identification of the initial lifecycle state
+  * Recording of the current lifecycle state
+  * Execution of permitted lifecycle transitions
+  * Retirement of the Infrastructure Environment when the Retirement conditions are satisfied
+  * Confirmation that the derived requirements collectively preserve the complete intent of MO-006
-The decomposition preserves ''MO-006'' as the stable parent requirement identifier. Each replacement requirement receives a lettered identifier and a separate requirement page.
+The decomposition preserves ''MO-006'' as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.
 ===== Proposed Statements =====
-The Original Requirement is replaced by the following independently identifiable normative requirements:
+The Original Requirement is decomposed into the following proposed replacement requirements:
 {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006#1|js navbar nocookie maxjs#1 id#crucible_mo_006_requirements_nav}}
+===== Requirement Status =====
+<todo>Review and approve the proposed decomposition of MO-006 into independently testable lifecycle association, initiation, state-recording, transition-execution, and Retirement requirements.</todo>
+<todo>Determine whether MO-006a through MO-006e collectively supersede MO-006.</todo>
+<todo>If MO-006a through MO-006e are accepted as the complete replacement for MO-006, mark MO-006 as superseded and preserve this page as the parent Traceability record.</todo>
+----
+===== Issues =====
+The following unresolved issues affect the decomposition of MO-006:
+<todo>Identify the Operational Lifecycles that may be associated with an Infrastructure Environment.</todo>
+<todo>Define how Crucible identifies the Operational Lifecycle revision associated with an Infrastructure Environment.</todo>
+<todo>Define the lifecycle state assigned when an Infrastructure Environment is created through an Infrastructure Deployment.</todo>
+<todo>Define the lifecycle states that Crucible records for an Infrastructure Environment.</todo>
+<todo>Define the lifecycle transitions allocated to Crucible.</todo>
+<todo>Define the conditions that permit each lifecycle transition.</todo>
+<todo>Define the behavior required when a requested lifecycle transition is not permitted.</todo>
+<todo>Define the conditions that permit Retirement of an Infrastructure Environment.</todo>
+<todo>Define the records preserved for lifecycle state changes, transitions, and Retirement.</todo>
+<todo>Determine whether MO-006a through MO-006e provide complete coverage of the approved intent of MO-006.</todo>
+----
+===== Notes for Editors =====
+This page should retain the stable parent requirement identifier ''MO-006''.
+This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace.
+The child requirements are leaf requirement pages and omit a trailing '':start'' from their namespaces.
+The explicit child-page links should remain while the proposed decomposition is being developed. After the child pages have been created and finalized, the explicit links may be removed because the ''indexmenu'' displays the child requirement pages contained within the MO-006 namespace.
+This page preserves:
+  * The Original Requirement
+  * The assessment of the Original Requirement
+  * The reason for decomposition
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to the proposed replacement requirements
+  * The unresolved cross-cutting issues affecting the decomposition
+  * The supersession decision
+The derived requirements should distinguish:
+  * Association of an Infrastructure Environment with an Operational Lifecycle revision
+  * Assignment of the initial lifecycle state
+  * Recording of the current lifecycle state
+  * Execution of lifecycle transitions
+  * Retirement of the Infrastructure Environment
+Lifecycle association identifies the lifecycle model governing an Infrastructure Environment.
+Lifecycle initiation identifies the first lifecycle state assigned to the Infrastructure Environment.
+Lifecycle state recording identifies the current state of the Infrastructure Environment.
+Lifecycle transition execution changes the Infrastructure Environment from one permitted lifecycle state to another.
+Retirement places the Infrastructure Environment into its terminal lifecycle state after the defined Retirement conditions are satisfied.
+The Original Requirement should not be marked as superseded until the requirement owner:
+  * Approves the proposed decomposition
+  * Approves the child requirements
+  * Defines the Operational Lifecycle association and revision rules
+  * Defines the initial lifecycle state
+  * Defines the lifecycle states and permitted transitions
+  * Defines the Retirement conditions
+  * Defines the required lifecycle records
+  * Confirms that the child requirements collectively preserve the complete approved intent of MO-006
+  * Confirms that no additional child requirements are required
+After supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment.
+Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records.
 ----