Differences

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

--- fxdemo:01-part:07-core-conceptual-elements:07-1-overview [2026/06/25 14:57] – removed - external edit (Unknown date) 127.0.0.1
+++ fxdemo:01-part:07-core-conceptual-elements:07-1-overview [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== 7.1 Overview ======
+[[fxdemo:01-part:start | Go to Top ]]
+The core conceptual elements define the basic architectural vocabulary used by the Financial Systems Archetype. These elements describe participants, [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]]s, [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identities]], [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]]s, information structures, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] classifications, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] before later parts map them to [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Model (LM)]]s, implementation artifacts, deployment artifacts, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] packages.
+Figure 7.1-1 summarises the primary relationships among the core conceptual elements defined in this section.
+  Node
+  ├── has Node Identity
+  ├── performs Node Role
+  ├── participates in Runtime Plane
+  └── uses Communication Endpoint
+          └── carries Data Structure Instance
+                  └── conforms to Data Structure Definition
+Figure 7.1-1: Core conceptual element relationships
+A [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] participates in the architecture through a stable [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]], one or more [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]]s, one or more [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]]s, and one or more [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]]s. [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]]s carry [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]]s. Each [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]] conforms to its [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]]. [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability_and_evidence|Traceability and Evidence]] apply across these relationships, enabling later parts to relate conceptual elements to [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Model (LM)]]s, implementation artifacts, deployment artifacts, and observed results.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>