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, and Evidence concerns.
This part begins the architecture defined by the document set. It defines the conceptual foundation for the Financial Systems Archetype, including the Classification Path model, core conceptual elements, Runtime Plane concepts, Traceability concepts, Evidence concepts, and separation-of-concerns model used by later parts.
This part establishes the vocabulary and conceptual boundaries that later documents must preserve. Later parts may specialize these concepts, map them to implementation technologies, deploy them in concrete environments, or test them through Evidence-producing scenarios. Later parts do not redefine the concepts defined here.
This part does not define the platform-independent Platform Independent Model (PIM), the FX Demo Logical Model (LM), the Phase 0 implementation mapping, the Phase 0 deployment model, the Crucible scenarios, the acceptance checks, the scripts, the repository structure, or the runtime Evidence. Those concerns belong to later parts of the document set or supporting repository documentation.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.