dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-003:start

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-d-requirements:part-01:p1-req-13-4-003:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-003:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P1-REQ-13-4-003 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +A [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]] SHALL uniquely distinguish a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] within a defined architectural context.
 +
 +===== Source =====
 +
 +Part 1, Section 13.4: Core Conceptual Element Requirements.
 +
 +===== Rationale =====
 +
 +A Node Identity provides the conceptual basis for distinguishing one Node from another within a defined architectural context. Unique distinction supports governance, accountability, traceability, policy evaluation, evidence collection, and operational interpretation.
 +
 +This requirement prevents ambiguity when the architecture refers to Nodes across diagrams, requirements, profiles, and later implementation mappings.
 +
 +===== Applies To =====
 +
 +This requirement applies to Node Identity definitions and references within the Conceptual Architecture.
 +
 +It applies specifically to:
 +
 +  * Node identification
 +  * Architectural context
 +  * Node distinction
 +  * Cross-reference consistency
 +  * Traceability involving Nodes
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that each Node Identity uniquely distinguishes a Node within a defined architectural context.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Node Identity has a defined architectural context
 +  * Node Identity distinguishes one Node from another
 +  * Node Identity does not substitute for a runtime process identifier
 +  * Later implementation identifiers map to Node Identity without redefining it
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-4-core-conceptual-element-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-002:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-011:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>