====== P1-REQ-13-4-011 ====== [[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]] ===== Statement ===== The Conceptual Architecture SHALL distinguish among a [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], a [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]], a [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]], a [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], a [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]], a [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]], a [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], an implementation artifact, and a deployment artifact. ===== Source ===== Part 1, Section 13.4: Core Conceptual Element Requirements. ===== Rationale ===== The core conceptual elements describe different architectural concerns. A Node, Node Role, Node Identity, Communication Endpoint, Data Structure Definition, Data Structure Instance, Runtime Plane, implementation artifact, and deployment artifact each serves a distinct purpose. Distinguishing these elements prevents identity, responsibility, communication, information, runtime purpose, implementation, and deployment concerns from collapsing into one another. ===== Applies To ===== This requirement applies to all uses of core conceptual elements within the Conceptual Architecture. It applies specifically to distinctions among: * Node * Node Role * Node Identity * Communication Endpoint * Data Structure Definition * Data Structure Instance * Runtime Plane * Implementation artifact * Deployment artifact ===== Verification ===== Verification SHALL confirm that the Conceptual Architecture distinguishes among the named core conceptual, implementation, and deployment elements. Verification activities include review checks confirming that: * Node, Node Role, and Node Identity remain distinct * Communication Endpoint remains distinct from Nodes and exchanged information * Data Structure Definition remains distinct from Data Structure Instance * Runtime Plane remains distinct from implementation and deployment artifacts * Implementation artifacts and deployment artifacts do not redefine conceptual elements ===== 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-012:start]] * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-013:start]] ===== Status ===== Draft ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.