Differences

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

--- fxdemo:01-part:07-core-conceptual-elements:07-3-node-identity [2026/06/25 15:05] – ↷ Page moved from fxdemo:01-part:07-3-node-identity to fxdemo:01-part:07-core-conceptual-elements:07-3-node-identity owen
+++ fxdemo:01-part:07-core-conceptual-elements:07-3-node-identity [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== 7.3 Node Identity ======
+[[fxdemo:01-part:start | Go to Top ]]
-**Discussion:**
+See the definition: [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]]
-Node Identity uniquely distinguishes a Node within a defined architectural, logical, implementation, or deployment context. It provides the basis for attribution, authorisation, monitoring, audit, provenance, replay, recovery, and evidence.
+----
-A Node Identity allows later parts to identify which Node produced information, consumed a Communication Endpoint, reported status, acknowledged a command, executed a Node Role, or generated evidence.
+<WRAP centeralign>
-A Node Identity exists at the architectural level. A deployment profile may associate a Node Identity with a container name, pod name, process identifier, host name, network address, certificate, service account, or other runtime identifier. Those identifiers do not replace the Node Identity.
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
-**Definition:**
+</WRAP>
-//identifier uniquely distinguishing a Node within a defined architectural context//
-**Source:**
-Adapted from FX Demo Reference Architecture, Section 2.1.16, Node Identity; generalised from implementation-profile identity to conceptual architectural identity.
-**Note:**
-A Node Identity is not a container name, pod name, host name, process identifier, user identity, organisation identity, network address, or repository path.
-**Example:**
-A Phase 0 implementation profile may assign a stable Node Identity to a health-monitoring Node so later reviewers can attribute its heartbeat records, status messages, audit entries, and evidence to the same architectural participant.