DIDO Solutions technical documentation and FX Demo knowledge base https://wiki.didosolutions.com/ 2026-08-22T21:21:24+00:00 https://wiki.didosolutions.com/ https://wiki.didosolutions.com/_media/wiki/logo.png text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/05-conceptual-architecture-principles/05-1-separation-of-concerns?rev=1784403224&do=diff 4.1 Separation of Concerns Go to Top The architecture separates conceptual meaning, logical Structure, domain specialization, implementation mapping, deployment mechanics, testability, and Evidence. This separation allows each layer to evolve without redefining the layers inside it. For example, a later implementation profile may realize a text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/05-conceptual-architecture-principles/05-2-platform-independence?rev=1784403224&do=diff 4.2 Platform Independence Go to Top The conceptual architecture does not depend on a specific technology, product, programming language, middleware, orchestration platform, modeling notation, Data serialisation format, or deployment target. Later parts may introduce technology-specific mappings. Those mappings realize the conceptual architecture for a specific purpose, but they do not define it. text/html 2026-07-11T18:15:07+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/05-conceptual-architecture-principles/05-3-classification-before-implementation?rev=1783793707&do=diff 4.3 Classification Before Implementation Go to Top The architecture classifies the governed financial scope before it defines implementation mechanisms. The Ecosphere, Ecosystem, and Domain model identifies the business and semantic scope of an archetype. These classification values do not act as runtime identifiers. They do not define DDS Domain IDs, Kubernetes namespaces, container names, pod names, topic names, text/html 2026-08-04T14:09:26+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/05-conceptual-architecture-principles/05-4-logical-meaning-before-physical-realisation?rev=1785852566&do=diff 4.4 Logical Meaning Before Physical Realization Go to Top The architecture defines logical meaning before physical realization. A Node has a Node Role and Node Identity before an implementation profile decides whether it runs as a process, container, pod, virtual machine, or service. A text/html 2026-07-18T19:33:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/05-conceptual-architecture-principles/05-5-traceability?rev=1784403224&do=diff 4.5 Traceability Go to Top Each layer preserves Traceability to the layer inside it. A logical element traces to the conceptual element it specializes in. An implementation artifact traces to the logical element it realizes. A deployment artifact traces to the implementation artifact it deploys. text/html 2026-07-11T18:15:17+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/05-conceptual-architecture-principles/05-6-evidence-orientation?rev=1783793717&do=diff 4.6 Evidence Orientation Go to Top The architecture treats Evidence as an architectural concern, not merely as a testing by-product. Financial Systems support defensible claims about Interpretation, execution, transformation, release, audit, and oversight. Later implementation and deployment profiles identify the text/html 2026-07-11T18:15:17+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/05-conceptual-architecture-principles/05-7-governance-of-meaning?rev=1783793717&do=diff 4.7 Governance of Meaning Go to Top The architecture protects the meaning of financial information across layers. Financial Data, control instructions, Interpretation logic, Semantic references, policy decisions, release actions, audit records, provenance Evidence, and test Evidence remain distinguishable. Systems that collapse those concerns become harder to govern, test, evolve, and defend. text/html 2026-07-11T18:15:17+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.didosolutions.com/fxdemo/01-part/05-conceptual-architecture-principles/start?rev=1783793717&do=diff 4. Conceptual Architecture Principles Go to Top The Financial Systems Archetype uses the following principles to protect conceptual meaning across later logical, implementation, deployment, and Evidence layers. Contents 05-conceptual-architecture-principles index ---------- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.