Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top Backlinks This is a list of pages that seem to link back to the current page. Audit Recording RoleCash-Flow Computation RoleContract State Management RoleExternal Oversight ParticipantFX Audit and Provenance NodeFX Audit RecordFX Audit Record EndpointFX Cash-Flow Computation NodeFX Cash-Flow ObligationFX Cash-Flow Obligation EndpointFX Command AcknowledgementFX Contract StateFX Contract State EndpointFX Contract State NodeFX Control CommandFX Control Command EndpointFX Health and Observability NodeFX Node StatusFX Node Status EndpointFX Policy and Release NodeFX Policy DecisionFX Policy Decision EndpointFX Provenance RecordFX Provenance Record EndpointFX Registry and Coordination NodeFX Release PackageFX Release Package EndpointFX Replay and Reconstruction NodeFX Replay RequestFX Replay Request EndpointFX Replay ResultFX Replay Result EndpointFX Semantic AssertionFX Semantic Interpretation EndpointFX Semantic Interpretation NodeFX Transaction CandidateFX Transaction Intake EndpointFX Transaction RecordFX Validation ResultFX Validation Result EndpointHealth Reporting RoleLogical Audit and Provenance PlaneLogical Policy and Release PlaneOversight Consumption RolePolicy Evaluation RoleProvenance Recording RoleRecordRegistry and Coordination RoleRelease Control RoleReplay and Reconstruction RoleSemantic Interpretation RoleStructural Validation RoleTransaction Intake Role1. ScopeForewordIntroduction1. Scope2. Relationship to Part 03.1 Traceability to SIP-RA3.2 Alignment with FDIS-RA3.3 Coverage of the Original FX Demo Reference Architecture3.4 Traceability Position3. Traceability to Parent and Source Architectures4.1 Separation of Concerns4.2 Platform Independence4.3 Classification Before Implementation4.4 Logical Meaning Before Physical Realization4.5 Traceability4.6 Evidence Orientation4.7 Governance of Meaning4. Conceptual Architecture Principles5.1 Overview5.2 Ecosphere5.3 Ecosystem5.4 Domain5.5 Classification Path5.6 Classification Values and Runtime Identifiers5.7 Classification and Governance5. Archetype Classification Model6.1 Overview6.2 Finance Ecosphere6.3 Monetary Ecosystem6.4 Foreign Exchange Domain6.5 Classification Inheritance for FX Profiles6.6 Future Financial Classifications6.7 Classification Governance6. Financial Systems Classification7.1 Overview7.2 Node7.3 Node Identity7.4 Node Role7.5 Runtime Plane7.6 Communication Endpoint7.7 Data Structure Definition7.8 Data Structure Instance7.9 Evidence7.107. Core Conceptual Elements8.1 Overview8.2 Control Plane8.3 Data Plane8.4 Health and Observability Plane8.5 Policy And Release Plane8.6 Audit And Provenance Plane8.7 Cross-Plane Relationships8. Conceptual Runtime Plane Model9.1 Overview9.2 Data9.3 Structure9.4 Semantics9.5 Interpretation9.6 Governance and Authority9.7 Traceability and Evidence9.8 Cross-Concern Relationships9. Separation of Concerns Model10.1 Overview10.2 Traceability Across Layers10.3 Conceptual Element to Logical Element / PIM10.4 Logical Element / PIM to Implementation Artifact / PSM10.5 Implementation Artifact / PSM to Deployment Artifact10.6 Deployment Artifact to Evidence10.7 Bidirectional Review and Impact Analysis10.8 Traceability Boundaries10. Conceptual Traceability Model11.1 Overview11.2 Conceptual Elements Remain Distinct11.3 Conceptual Architecture Does Not Prescribe Realization Mechanisms11.4 Classification Values Do Not Define Runtime Boundaries11.5 Runtime Planes Remain Conceptual Classifications11.6 Implementation Mappings Do Not Redefine Concepts11.7 Deployment Artifacts Do Not Redefine Implementation Artifacts11.8 Evidence Supports Claims11.9 Traceability Preserves Layering11.10 Local Profiles Must Preserve Parent Meaning11.11 Conceptual Constraints Summary11. Conceptual Rules and Constraints12.1 Overview12.2 Conceptual Elements Become Logical Elements12.3 Logical Architecture Preserves Conceptual Meaning12.4 Logical Architecture Remains Platform Independent12.5 Logical Architecture Supports Domain Profiles12.6 Logical Architecture Provides the Basis for Implementation Profiles12.7 Traceability from Part 1 to Part 212.8 Boundary Between Part 1 and Part 212. Relationship to the Logical Architecture / PIM13.1 Overview13. Conceptual RequirementsForewordIntroduction1. ScopeForewordIntroductionForewordFinancial Systems Archetype Guidance Documents fxdemo/01-part/start.txt Last modified: 2026/07/01 17:48by nick_dido