====== P2-REQ-16-3-008 ======

[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]

===== Statement =====

Logical Node Lifecycle State SHALL identify the logical operational condition associated with a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]].

===== Source =====

Part 2, Section 16.3: Logical Node Requirements.

===== Rationale =====

Logical Node Lifecycle State provides a platform-independent representation of a Logical Node's operational condition. Lifecycle states support monitoring, governance, operational coordination, review, and later implementation mapping without prescribing runtime mechanisms.

===== Applies To =====

This requirement applies to Logical Node Lifecycle State definitions throughout the Logical Architecture.

It applies specifically to:

  * Logical Nodes;
  * Lifecycle modeling;
  * Health monitoring; and
  * Domain Logical Profiles.

===== Verification =====

Verification SHALL confirm that Logical Node Lifecycle States identify the logical operational condition associated with Logical Nodes.

Verification activities should include review checks confirming that:

  * lifecycle states are explicitly defined;
  * lifecycle states apply to Logical Nodes;
  * lifecycle states support logical operational modeling; and
  * lifecycle definitions remain platform independent.

===== Traceability =====

This requirement supports traceability between Logical Nodes and their logical operational conditions.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-001]]
  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-002]]
  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-003]]

Related source section:

  * [[fxdemo:02-part:16-logical-requirements:16-3-logical-node-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>