Foreword

Go to Top

The Financial Systems Archetype document set provides a layered architecture for applying structured information processing principles to financial systems. Part 0: Document Set Overview and Reader’s Guide explains the document set, the layered structure, the reader’s guide, and the rules for preserving separation among conceptual, logical, implementation, deployment, testability, and evidence concerns.

Part 1: Conceptual Architecture defines the Conceptual Architecture. It establishes the conceptual foundation for the Financial Systems Archetype, including classification, core conceptual elements, Runtime Plane, traceability, evidence, and separation-of-concerns concepts.

Part 2: Distributed Node-Based Logical Architecture defines a distributed, node-based Logical Architecture as a Platform Independent Model. It specializes the concepts defined in Part 1 into platform-independent logical Nodes, logical Communication Endpoints, logical information structures, logical Runtime Planes, logical interaction patterns, logical governance relationships, and logical traceability relationships.

Part 3: FX Demo Logical Profile defines the FX Demo Logical Profile. It specializes the Part 2 Logical Architecture / PIM for the Foreign Exchange Domain within the Finance Ecosphere and Monetary Ecosystem. It defines FX-specific logical Nodes, logical 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, REST bindings, 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.