Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:n:node_role [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido
+++ dido: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 5: / Line 5: @@
 ===== Discussion =====
-A Node Role identifies the responsibility a [[dido: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.
-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 =====
-//responsibility performed by a [[dido: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 =====
@@ Line 19: / Line 19: @@
 ===== Note =====
-A Node Role is not itself a deployed participant. A [[dido: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 =====
 Examples of Node Roles include service registration, health monitoring, transaction intake, validation, attestation, policy evaluation, release control, persistence, replay, audit recording, and provenance recording.