Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:f:financial_node [2026/08/04 07:09] – ↷ Page moved from dido:99_annexes:annex-b-terms-and-definitions:n:financial_node to dido:99_annexes:annex-b-terms-and-definitions:f:financial_node nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:f:financial_node [2026/08/04 07:31] (current) – nick_dido
@@ Line 1: / Line 1: @@
 ====== Financial Node ======
-[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 ===== Discussion =====
-A Node identifies an architectural participant in a distributed financial system. It provides a stable point of responsibility for communication, attribution, monitoring, governance, and traceability.
+A Financial Node is a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] that participates in a distributed financial system.
-A Node performs one or more [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role| Node Roles]], has a [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity]], participates in one or more Runtime Planes, and exchanges information through one or more Communication Endpoints.
+A Financial Node inherits the identity, role, responsibility, communication, governance, attribution, monitoring, Evidence, Provenance, and Traceability characteristics of a Node. Its assigned roles concern financial information, financial activities, financial agreements, financial events, financial calculations, financial obligations, financial controls, or financial outcomes.
-A Node exists at the conceptual level. Later parts may realize a Node as a process, container, pod, service, virtual machine, gateway, external interface, analytical engine, monitoring component, persistence service, or other deployed participant. Those realisations do not redefine the concept of Node.
-A Node may host or use one or more software modules, analytical engines, rules engines, policy components, persistence mechanisms, or adapters. The Node remains distinct from the software modules or implementation artifacts that it uses.
+A Financial Node provides a stable point of responsibility for:
+  * Financial-information processing
+  * Financial-event processing
+  * Financial calculations
+  * Financial state management
+  * Financial validation
+  * Financial policy evaluation
+  * Financial agreement evaluation
+  * Regulatory evaluation
+  * Communication
+  * Attribution
+  * Monitoring
+  * Governance
+  * Evidence
+  * Provenance
+  * Traceability
+A Financial Node performs one or more [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Roles]], has a [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]], participates in one or more Runtime Planes, and exchanges information through one or more Communication Endpoints.
+A Financial Node exists at the conceptual or logical level. An implementation can realize a Financial Node as a:
+  * Process
+  * Container
+  * Pod
+  * Service
+  * Virtual machine
+  * Physical machine
+  * Gateway
+  * External interface
+  * Analytical engine
+  * Rules engine
+  * Policy component
+  * Monitoring component
+  * Persistence service
+  * Human-operated participant
+  * Other deployed participant
+The realization does not redefine the Financial Node.
+A Financial Node can host or use software modules, analytical engines, rules engines, policy components, persistence mechanisms, communication adapters, and other implementation artifacts. The Financial Node remains distinct from the software and artifacts it uses.
 ===== Definition =====
-//architectural participant in a distributed financial system//
+//[[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] that participates in a [[dido:99_annexes:annex-b-terms-and-definitions:d:distributed_financial_system|Distributed Financial System]]//
 ===== Source =====
-Adapted from FX Demo Reference Architecture, Section 2.1.1, Node; generalized from “deployed participant” to “architectural participant” for use in the Financial Systems Archetype conceptual layer.
+Adapted from:
+  * FX Demo Reference Architecture, Section 2.1.1, Node
+  * Financial Systems Archetype conceptual and logical architecture
+  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
+The original definition described an “architectural participant in a distributed financial system.” This revision defines Financial Node as a specialization of Node and preserves the financial-system participation characteristic.
 ===== Note =====
-A Node is not a Communication Endpoint, Data Structure Definition, Data Structure Instance, software module, container, pod, process, runtime host, or deployment artifact.
+Every Financial Node is a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]. A Node is not necessarily a Financial Node.
+A Financial Node is not defined by its implementation technology. A process, container, pod, service, virtual machine, physical machine, or software module can realize or support a Financial Node but does not by itself constitute the Financial Node.
+A Financial Node is distinct from:
+  * A Communication Endpoint
+  * A Data Structure Definition
+  * A Data Structure Instance
+  * A software module
+  * A container
+  * A pod
+  * A process
+  * A runtime host
+  * A Deployment Target
+  * A deployment artifact
+A Financial Node can participate in a system that also contains Nodes that do not perform financial roles. Monitoring, infrastructure, communication, security, or administrative Nodes do not become Financial Nodes solely because they support a distributed financial system.
+A supporting Node becomes a Financial Node when its assigned role forms part of the financial behavior, financial state, financial controls, or financial outcomes of the distributed financial system.
 ===== Example =====
-An FX validation service, ACTUS cash-flow computation service, policy release service, or health monitoring service may act as a Node in a later logical profile or implementation profile.
+An FX validation service acts as a Financial Node when it evaluates an FX transaction against the applicable structural, lifecycle, agreement, or policy constraints.
+An ACTUS cash-flow computation service acts as a Financial Node when it calculates contractually defined financial events and cash flows.
+A policy release service acts as a Financial Node when it determines whether a proposed financial state transition satisfies the applicable release policies.
+A general infrastructure-monitoring service remains a Node but does not necessarily become a Financial Node when it observes only computing-resource health and performs no assigned financial role.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>