This section identifies the normative requirements for core conceptual elements established by Part 1. The canonical requirement statements are maintained in Annex C: Requirements, Part 1.
Table 13.4-1: Part 1 core conceptual element requirements.
| Requirement ID | Statement |
|---|---|
| P1-REQ-13-4-001 |
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. |
| P1-REQ-13-4-002 |
The Conceptual Architecture SHALL distinguish a Node as an architectural participant in a distributed Financial System. |
| P1-REQ-13-4-003 |
A Node Identity SHALL uniquely distinguish a Node within a defined architectural context. |
| P1-REQ-13-4-004 |
|
| P1-REQ-13-4-005 |
A Runtime Plane SHALL classify runtime communication and behavior by architectural purpose. |
| P1-REQ-13-4-006 |
A Communication Endpoint SHALL identify a point of information exchange used by one or more Nodes. |
| P1-REQ-13-4-007 |
A Data Structure Definition SHALL describe the Structure, meaning, and constraints of a class of information. |
| P1-REQ-13-4-008 |
A Data Structure Instance SHALL identify a populated occurrence of a Data Structure Definition. |
| P1-REQ-13-4-009 |
Evidence SHALL identify recorded information supporting a claim. |
| P1-REQ-13-4-010 |
Traceability SHALL identify a relationship connecting one architectural, logical, implementation, deployment, or Evidence element to another. |
| P1-REQ-13-4-011 |
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 artifact, and a deployment artifact. |
| P1-REQ-13-4-012 |
The Conceptual Architecture SHALL distinguish a Data Structure Definition from a Data Structure Instance. |
| P1-REQ-13-4-013 |
The Conceptual Architecture SHALL distinguish a Communication Endpoint from the information exchanged through that endpoint. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.