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 0 and Part 13.1 Traceability to SIP-RA3.2 Alignment with FDIS-RA3.3 Traceability to Part 1 Conceptual Architecture3.4 Coverage of the Original FX Demo Reference Architecture3.5 Traceability Position3. Traceability to Parent and Source Architectures4.1 Distributed Node-Based Architecture4.2 Explicit Communication over Implicit Coupling4.3 Platform Independence4.4 Logical Separation of Runtime Planes4.5 Explicit Information Structures4.6 Traceability from Concept to Logical Model4.7 Evidence-Oriented Logical Design4.8 Policy-Governed Sharing Without Centralised Data Routing4. Logical Architecture Principles5.1 Overview5.2 Logical Architecture Context5.3 Distributed Logical Node Network5.4 Logical Communication Model5.5 Logical Information Model5.6 Logical Runtime Plane Model5.7 Logical Traceability Model5. Logical Architecture Overview6.1 Overview6.2 Logical Node6.3 Logical Node Identity6.4 Logical Node Role6.5 Logical Node Responsibility6.6 Logical Node Boundary6.7 Logical Node Collaboration6.8 Logical Node Lifecycle State6. Logical Node Model7.1 Overview7.2 Logical Communication Endpoint7.3 Communication Role7.4 Publisher Role7.5 Subscriber Role7.6 Requester Role7.7 Responder Role7.8 Command Producer Role7.9 Command Consumer Role7.10 Event Producer Role7.11 Event Consumer Role7.12 Communication Direction and Coupling7.13 Communication Pattern Independence7. Logical Communication Model8.1 Overview8.2 Logical Data Structure Definition8.3 Logical Data Structure Instance8.4 Logical Message8.5 Logical Event8.6 Logical Command8.7 Logical Acknowledgement8.8 Logical Assertion8.9 Logical Record8.10 Logical Information Lineage8. Logical Information Model9.1 Overview9.2 Logical Control Plane9.3 Logical Data Plane9.4 Logical Health and Observability Plane9.5 Logical Policy and Release Plane9.6 Logical Audit and Provenance Plane9.7 Cross-Plane Logical Relationships9. Logical Runtime Plane Model10.1 Overview10.2 Register Node10.3 Report Node Status10.4 Publish Domain Information10.5 Subscribe to Domain Information10.6 Issue Control Command10.7 Acknowledge Control Command10.8 Request Policy Decision10.9 Enforce Policy Decision and Produce Authorized Release10.10 Record Audit and Provenance10.11 Replay or Reconstruct Information10.12 Logical Interaction Pattern Summary10. Logical Interaction Patterns11.1 Overview11.2 Logical Ownership of Definitions11.3 Logical Versioning11.4 Logical Compatibility11.5 Logical Change Control11.6 Logical Admission RulesLogical Policy Constraints11. Logical Governance Model12.1 Overview12.2 Part 1 Concept to Part 2 Logical Element12.3 Logical Node Traceability12.4 Logical Endpoint Traceability12.5 Logical Data Structure Traceability12.6 Logical Runtime Plane Traceability12.7 Logical Interaction Traceability12.8 Logical Evidence Traceability12.9 Logical Traceability Summary12. Logical Traceability Model13.1 Overview13.2 How Domain Profiles Specialize the Logical Architecture13.3 Domain Profile Additions13.4 What Domain Profiles Preserve13.5 Relationship to the FX Demo Logical Profile13.6 Boundary Between Part 2 and Domain Logical Profiles13. Relationship to Domain Logical Profiles14.1 Overview14.2 Logical Elements Prepared for Technology Mapping14.3 Communication Technology Independence14.4 Data Representation Independence14.5 Execution and Deployment Independence14.6 Implementation Mapping Boundaries14.7 Relationship to Phase 0 Implementation Profile14.8 Boundary Between Part 2 and Implementation Profiles14. Relationship to Implementation Profiles / PSM15.1 Overview15.2 Logical Nodes Remain Distinct from Runtime Deployments15.3 Logical Endpoints Remain Distinct from Communication Technologies15.4 Logical Data Structures Remain Distinct from Serialisation Formats15.5 Logical Runtime Planes Remain Distinct from Implementation Groupings15.6 Logical Interactions Remain Traceable15.7 Logical Architecture Does Not Prescribe Deployment Topology15.8 Logical Architecture Does Not Prescribe Communication Pattern Implementation15.9 Logical Architecture Does Not Prescribe Governance Tooling15.10 Domain Profiles Preserve the Logical Architecture15.11 Implementation Profiles Preserve the Logical Architecture15.12 Logical Constraints Summary15. Logical Rules and Constraints16. Logical RequirementsForewordIntroduction1. ScopeForewordFinancial Systems Archetype Guidance Documents fxdemo/02-part/start.txt Last modified: 2026/07/15 09:05by nick_dido