Differences

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

--- fxdemo:01-part:13-conceptual-requirements:13-4-core-conceptual-element-requirements [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:13-4-core-conceptual-element-requirements to fxdemo:01-part:13-conceptual-requirements:13-4-core-conceptual-element-requirements owen
+++ fxdemo:01-part:13-conceptual-requirements:13-4-core-conceptual-element-requirements [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== 13.4 Core Conceptual Element Requirements ======
-[[fxdemo:01-part:start | Go to Top ]]
+[[fxdemo:01-part:13-conceptual-requirements:start | Go to Conceptual Requirements]]
-  - The Conceptual Architecture SHALL define Node, Node Identity, Node Role, Runtime Plane, Communication Endpoint, Data Structure Definition, Data Structure Instance, Evidence, and Traceability as core conceptual elements.
+This section identifies the normative requirements for core conceptual elements established by Part 1. The canonical requirement statements are maintained in [[dido:99_annexes:annex-d-requirements:part-01:start|Annex C: Requirements, Part 1]].
-  - The Conceptual Architecture SHALL distinguish a Node as an architectural participant in a distributed financial system.
-  - A Node Identity SHALL uniquely distinguish a Node within a defined architectural context.
-  - A Node Role SHALL identify a responsibility performed by a Node.
-  - A Runtime Plane SHALL classify runtime communication and behaviour by architectural purpose.
-  - A Communication Endpoint SHALL identify a point of information exchange used by one or more Nodes.
-  - A Data Structure Definition SHALL describe the structure, meaning, and constraints of a class of information.
-  - A Data Structure Instance SHALL identify a populated occurrence of a Data Structure Definition.
-  - Evidence SHALL identify recorded information supporting a claim.
-  - Traceability SHALL identify a relationship connecting one architectural, logical, implementation, deployment, or evidence element to another.
-  - The Conceptual Architecture SHALL distinguish among a Node, a Node Role, a Node Identity, a Communication Endpoint, a Data Structure Definition, a Data Structure Instance, a Runtime Plane, an implementation artefact, and a deployment artefact.
-  - The Conceptual Architecture SHALL distinguish a Data Structure Definition from a Data Structure Instance.
-  - The Conceptual Architecture SHALL distinguish a Communication Endpoint from the information exchanged through that endpoint.
+<WRAP table-caption>
+**Table 13.4-1:** Part 1 core conceptual element requirements.
+</WRAP>
+^ Requirement ID ^ Statement ^
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-001:start|P1-REQ-13-4-001]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-001:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-002:start|P1-REQ-13-4-002]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-002:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-003:start|P1-REQ-13-4-003]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-003:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-004:start|P1-REQ-13-4-004]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-004:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-005:start|P1-REQ-13-4-005]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-005:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-006:start|P1-REQ-13-4-006]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-006:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-007:start|P1-REQ-13-4-007]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-007:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-008:start|P1-REQ-13-4-008]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-008:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-009:start|P1-REQ-13-4-009]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-009:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-010:start|P1-REQ-13-4-010]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-010:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-011:start|P1-REQ-13-4-011]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-011:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-012:start|P1-REQ-13-4-012]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-012:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-013:start|P1-REQ-13-4-013]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-013:start#statement&noheader&nofooter}} |
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>