The Financial Systems Archetype document set provides a layered architecture for applying structured information processing principles to financial systems. Part 0 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 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 defines a distributed, node-based Logical Architecture as a Platform-Independent Model (PIM). It specialises 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 defines the FX Demo Logical Profile. It specialises 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.
Part 4 defines the Phase 0 Implementation Profile / Platform-Specific Model (PSM). It maps selected elements of the FX Demo Logical Profile to Phase 0 implementation technologies, implementation artefacts, data representation artefacts, communication artefacts, generated artefacts, repository artefacts, implementation conventions, and traceability relationships.
This part defines a phase-specific implementation profile. The Phase 0 Implementation Profile / PSM establishes the implementation baseline for the Phase 0 FX Demo. Later development phases may define additional implementation profiles that extend, refine, supersede, or replace this profile while preserving traceability to the applicable conceptual, logical, and FX logical profile elements.
This part introduces the selected Phase 0 implementation context, including DDS, IDL, Quality of Service (QoS) profiles, generated types, implementation Nodes, implementation modules, scripts, repository structure, and supporting implementation artefacts. These implementation choices realise selected Part 3 logical elements for the Phase 0 FX Demo. They do not redefine the Part 1 Conceptual Architecture, the Part 2 Logical Architecture / PIM, or the Part 3 FX Demo Logical Profile.
This part also establishes the relationship between the Phase 0 Implementation Profile / PSM and the Phase 0 Developer Handbook. Coding for Phase 0 does not begin until the Developer Handbook defines the applicable file-header conventions, coding standards, naming conventions, generated-file rules, logging conventions, exception-handling patterns, repository workflow, and review expectations.
This part does not define deployment topology, runtime evidence, acceptance evidence, operational dashboards, Kubernetes or K3s deployments, Crucible scenario execution, or final test results. Part 5 addresses deployment, testability, runtime operation, observation, and evidence for the selected Phase 0 implementation.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.