====== Foreword ======

[[fxdemo:03-part:start|Go to Top]]

The Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set provides a layered architecture for applying structured information processing principles to [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|financial systems]]. [[fxdemo:00-part:start]] explains the document set, the layered structure, the reader’s guide, and the rules for preserving separation among conceptual, logical, implementation, deployment, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] concerns.

[[fxdemo:01-part:start]] defines the Conceptual Architecture. It establishes the conceptual foundation for the Financial Systems Archetype, including classification, core conceptual elements, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]], evidence, and separation-of-concerns concepts.

[[fxdemo:02-part:start]] defines a distributed, node-based Logical Architecture as a [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model]]. It specializes the concepts defined in Part 1 into platform-independent logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical Runtime Planes, logical interaction patterns, logical governance relationships, and logical traceability relationships.

[[fxdemo:03-part:start]] defines the FX Demo Logical Profile. It specializes the Part 2 Logical Architecture / PIM for the [[dido:99_annexes:annex-b-terms-and-definitions:f:foreign_exchange_domain|Foreign Exchange Domain]] within the [[dido:99_annexes:annex-b-terms-and-definitions:f:finance_ecosphere|Finance Ecosphere]] and [[dido:99_annexes:annex-b-terms-and-definitions:m:monetary_ecosystem|Monetary Ecosystem]]. It defines FX-specific logical Nodes, logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Roles]], logical Communication Endpoints, logical information structures, logical Runtime Planes, logical interaction patterns, logical governance relationships, and logical traceability relationships.

This part remains platform-independent. It does not define DDS mappings, IDL structures, Quality of Service (QoS) profiles, Python implementation patterns, Protocol Buffers mappings, [[dido:99_annexes:annex-b-terms-and-definitions:r:rest|REST]] bindings, [[dido:99_annexes:annex-b-terms-and-definitions:r:rpc|RPC]] bindings, container-image mappings, Kubernetes or K3s deployment, Crucible scenarios, acceptance checks, scripts, repository structure, or runtime evidence. Later parts and supporting repository documentation address those concerns.