dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Logical Node Role ======
  
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]]
 +
 +===== Discussion =====
 +
 +A Logical Node Role identifies a platform-independent responsibility assigned to, or performed by, a Logical Node.
 +
 +Logical Node Roles allow the architecture to describe what a Logical Node does without tying the responsibility to any specific technology, process, service, container, pod, or deployment unit. A Logical Node performs one or more Logical Node Roles. The Logical Architecture assigns the same Logical Node Role to multiple Logical Nodes when redundancy, partitioning, jurisdictional separation, organizational separation, or parallel processing requires that distribution.
 +
 +Logical Node Roles support review and traceability by connecting responsibilities to Nodes, interactions, Runtime Planes, information structures, governance expectations, and evidence expectations.
 +
 +===== Definition =====
 +
 +//Platform-independent responsibility assigned to or performed by a Logical Node.//
 +
 +===== Source =====
 +
 +Specialization of Node Role from Part 1, Section 7.4; generalises the Node Role Framework from the original FX Demo Reference Architecture.
 +
 +===== Note =====
 +
 +A Logical Node Role is not itself a Logical Node. A Logical Node performs a Logical Node Role.
 +
 +===== Example =====
 +
 +Examples of Logical Node Roles include service registration, health monitoring, configuration coordination, schema and model version coordination, transaction intake, validation, semantic interpretation, policy evaluation, release control, audit recording, provenance recording, persistence, replay, and oversight support.
 +
 +----
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]]