dido:99_annexes:annex-b-terms-and-definitions:n: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:n:node_role [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node_role to dido:99_annexes:annex-b-terms-and-definitions:n:node_role nick_didodido:99_annexes:annex-b-terms-and-definitions:n:node_role [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Node Role ====== ====== Node Role ======
  
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]+[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
  
-A Node Role identifies the responsibility a [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node|Node]] performs within the architecture. Node Roles allow the architecture to describe what a Node does without binding that responsibility to a specific technology, process, container, pod, or deployment unit.+A Node Role identifies the responsibility a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] performs within the architecture. Node Roles allow the architecture to describe what a Node does without binding that responsibility to a specific technology, process, container, pod, or deployment unit.
 A Node may perform one Node Role or multiple Node Roles. A logical architecture may keep several roles together within a single Node. At the same time, a later implementation or deployment profile may separate those roles across multiple Nodes for scaling, resilience, governance, jurisdictional separation, or operational control. A Node may perform one Node Role or multiple Node Roles. A logical architecture may keep several roles together within a single Node. At the same time, a later implementation or deployment profile may separate those roles across multiple Nodes for scaling, resilience, governance, jurisdictional separation, or operational control.
-Node Roles support traceability by connecting architectural responsibility to logical design, implementation artefacts, deployment artefacts, and evidence.+Node Roles support traceability by connecting architectural responsibility to logical design, implementation artifacts, deployment artifacts, and evidence.
  
 ===== Definition ===== ===== Definition =====
  
-//responsibility performed by a [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node|Node]] within the architecture//+//responsibility performed by a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] within the architecture//
  
 ===== Source ===== ===== Source =====
Line 19: Line 19:
 ===== Note ===== ===== Note =====
  
-A Node Role is not itself a deployed participant. A [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node|Node]] performs a Node Role.+A Node Role is not itself a deployed participant. A [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] performs a Node Role.
  
 ===== Example ===== ===== Example =====
  
 Examples of Node Roles include service registration, health monitoring, transaction intake, validation, attestation, policy evaluation, release control, persistence, replay, audit recording, and provenance recording. Examples of Node Roles include service registration, health monitoring, transaction intake, validation, attestation, policy evaluation, release control, persistence, replay, audit recording, and provenance recording.
  • dido/99_annexes/annex-b-terms-and-definitions/n/node_role.1783793680.txt.gz
  • Last modified: 2026/07/11 11:14
  • by nick_dido