| Second, it aligns with **FDIS-RA** as a financial-domain interpretation architecture. FDIS-RA provides precedent for treating semantic [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]], validation, comparability, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], auditability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] as architectural concerns in financial and regulated reporting environments. | Second, it aligns with **FDIS-RA** as a financial-domain interpretation architecture. FDIS-RA provides precedent for treating semantic [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]], validation, comparability, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], auditability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] as architectural concerns in financial and regulated reporting environments. |
| Third, it normalises source material from the original **FX Demo Reference Architecture**. The original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture (RA)]] combined conceptual definitions, logical architecture, DDS-oriented implementation concerns, Quality of Service (QoS), topics, [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]]s, common data types, ontology concerns, [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]]s, use cases, and catalogues. The Financial Systems Archetype document set separates those concerns into conceptual, logical, profile, implementation, deployment, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] layers. | Third, it normalizes source material from the original **FX Demo Reference Architecture**. The original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture (RA)]] combined conceptual definitions, logical architecture, DDS-oriented implementation concerns, Quality of Service (QoS), topics, [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]]s, common data types, ontology concerns, [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]]s, use cases, and catalogs. The Financial Systems Archetype document set separates those concerns into conceptual, logical, profile, implementation, deployment, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] layers. |