dido:99_annexes:annex-b-terms-and-definitions:n:node_identity

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_identity [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:n:node_identity [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Node Identity ======
  
 +[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Node Identity uniquely distinguishes a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] within a defined architectural, logical, implementation, or deployment context. It provides the basis for attribution, authorization, 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.
 +
 +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.
 +
 +
 +===== Definition =====
 +
 +//identifier uniquely distinguishing a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|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, organization identity, network address, or repository path.
 +
 +===== Example =====
 +
 +A Phase 0 implementation profile may assign a stable Node Identity to a health-monitoring [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] so later reviewers can attribute its heartbeat records, status messages, audit entries, and evidence to the same architectural participant.