Part 3: FX Demo Logical Profile

Go to The FX Demo Root

Part 3 defines the FX Demo Logical Profile for the Foreign Exchange domain. It applies the logical architecture from Part 2 to the FX Demo context by identifying the domain-specific logical scope, classification values, stakeholders, information flows, and node responsibilities that support a governed foreign-exchange demonstration. Part 3 does not select implementation technology. It narrows the platform-independent architecture into a domain profile that Part 4 maps onto the Phase 0 implementation baseline.

* Part 3: FX Demo Logical Profile

• Foreword
• Introduction
• 1. Scope
• 2. Relationship to Parts 0, 1, and 2
• 3. Traceability to Parent and Source Architectures

  • 3.1 Traceability to SIP-RA
  • 3.2 Alignment with FDIS-RA
  • 3.3 Traceability to Part 1 Conceptual Architecture
  • 3.4 Traceability to Part 2 Distributed Node-Based Logical Architecture / PIM
  • 3.5 Coverage of the Original FX Demo Reference Architecture
  • 3.6 Traceability Position
• 4. FX Demo Logical Profile Principles

  • 4.1 Domain Specialization without Conceptual Redefinition
  • 4.2 FX Domain Scope before Implementation
  • 4.3 Distributed FX Node Network
  • 4.4 Explicit FX Communication Endpoints
  • 4.5 FX Information Structures before Serialisation
  • 4.6 Runtime Plane Separation in the FX Demo
  • 4.7 Traceability from Concept to Logical Profile
  • 4.8 Evidence-Oriented FX Logical Design
  • 4.9 Phase Extension Without FX Logical Redefinition
• 5. FX Demo Logical Profile Overview

  • 5.1 Overview
  • 5.2 FX Demo Classification Path
  • 5.3 FX Demo Logical Architecture Context
  • 5.4 FX Demo Logical Node Network
  • 5.5 FX Demo Logical Communication Model
  • 5.6 FX Demo Logical Information Model
  • 5.7 FX Demo Logical Runtime Plane Model
  • 5.8 FX Demo Logical Traceability Model
• 6. FX Demo Logical Node Model

  • 6.1 Overview
  • 6.2 FX Transaction Intake Node
  • 6.3 FX Validation Node
  • 6.4 FX Semantic Interpretation Node
  • 6.5 FX Contract State Node
  • 6.6 FX Cash-Flow Computation Node
  • 6.7 FX Policy and Release Node
  • 6.8 FX Audit and Provenance Node
  • 6.9 FX Health and Observability Node
  • 6.10 FX Registry and Coordination Node
  • 6.11 FX Replay and Reconstruction Node
  • 6.12 External Oversight Participant
• 7. FX Demo Logical Node Roles

  • 7.1 Overview
  • 7.2 Transaction Intake Role
  • 7.3 Structural Validation Role
  • 7.4 Semantic Interpretation Role
  • 7.5 Contract State Management Role
  • 7.6 Cash-Flow Computation Role
  • 7.7 Policy Evaluation Role
  • 7.8 Release Control Role
  • 7.9 Audit Recording Role
  • 7.10 Provenance Recording Role
  • 7.11 Health Reporting Role
  • 7.12 Registry and Coordination Role
  • 7.13 Replay and Reconstruction Role
  • 7.14 Oversight Consumption Role
• 8. FX Demo Logical Communication Model

  • 8.1 Overview
  • 8.2 FX Transaction Intake Endpoint
  • 8.3 FX Validation Result Endpoint
  • 8.4 FX Semantic Interpretation Endpoint
  • 8.5 FX Contract State Endpoint
  • 8.6 FX Cash-Flow Obligation Endpoint
  • 8.7 FX Policy Decision Endpoint
  • 8.8 FX Release Package Endpoint
  • 8.9 FX Audit Record Endpoint
  • 8.10 FX Provenance Record Endpoint
  • 8.11 FX Node Status Endpoint
  • 8.12 FX Control Command Endpoint
  • 8.13 FX Replay Request Endpoint
  • 8.14 FX Replay Result Endpoint
• 9. FX Demo Logical Information Model

  • 9.1 Overview
  • 9.2 FX Transaction Candidate
  • 9.3 FX Transaction Record
  • 9.4 FX Validation Result
  • 9.5 FX Semantic Assertion
  • 9.6 FX Contract State
  • 9.7 FX Cash-Flow Obligation
  • 9.8 FX Policy Decision
  • 9.9 FX Release Package
  • 9.10 FX Audit Record
  • 9.11 FX Provenance Record
  • 9.12 FX Node Status
  • 9.13 FX Control Command
  • 9.14 FX Command Acknowledgement
  • 9.15 FX Replay Request
  • 9.16 FX Replay Result
• 10. FX Demo Runtime Plane Model

  • 10.1 Overview
  • 10.2 Logical Control Plane
  • 10.3 Logical Data Plane
  • 10.4 Logical Health and Observability Plane
  • 10.5 Logical Policy and Release Plane
  • 10.6 Logical Audit and Provenance Plane
  • 10.7 Cross-Plane Relationships in the FX Demo
• 11. FX Transaction and Contract Lifecycle Model

  • 11.1 Overview
  • 11.2 FX Transaction Lifecycle States
  • 11.3 FX Contract State Transitions
  • 11.4 Validation-Controlled Transitions
  • 11.5 Interpretation-Controlled Transitions
  • 11.6 Cash-Flow Computation Triggers
  • 11.7 Policy and Release State Considerations
  • 11.8 Audit and Provenance State Records
• 12. FX Demo Logical Interaction Patterns

  • 12.1 Overview
  • 12.2 Register FX Logical Node
  • 12.3 Report FX Node Status
  • 12.4 Intake FX Transaction Candidate
  • 12.5 Validate FX Transaction Candidate
  • 12.6 Interpret FX Transaction Semantics
  • 12.7 Establish or Update FX Contract State
  • 12.8 Compute FX Cash-Flow Obligations
  • 12.9 Request FX Policy Decision
  • 12.10 Release FX Information to Oversight Participant
  • 12.11 Record FX Audit and Provenance
  • 12.12 Replay or Reconstruct FX Information
  • 12.13 FX Logical Interaction Pattern Summary
• 13. FX Demo Logical Governance Model

  • 13.1 Overview
  • 13.2 FX Logical Ownership of Definitions
  • 13.3 FX Logical Versioning
  • 13.4 FX Logical Compatibility
  • 13.5 FX Logical Change Control
  • 13.6 FX Logical Admission Rules
  • 13.7 FX Logical Policy Constraints
  • 13.8 FX Logical Governance Summary
• 14. FX Demo Logical Traceability Model

  • 14.1 Overview
  • 14.2 Part 1 Concept to FX Logical Profile Element
  • 14.3 Part 2 Logical Element to FX Logical Profile Element
  • 14.4 FX Node Traceability
  • 14.5 FX Endpoint Traceability
  • 14.6 FX Information Structure Traceability
  • 14.7 FX Runtime Plane Traceability
  • 14.8 FX Interaction Traceability
  • 14.9 FX Evidence Traceability
  • 14.10 FX Logical Traceability Summary
• 15. Relationship to Implementation Profiles / PSM

  • 15.1 Overview
  • 15.2 FX Logical Elements Prepared for Technology Mapping
  • 15.3 FX Communication Technology Independence
  • 15.4 FX Data Representation Independence
  • 15.5 FX Execution and Deployment Independence
  • 15.6 Boundary Between Part 3 and Part 4
  • 15.7 Relationship to Phase 0 Implementation Profile
• 16. FX Demo Logical Rules and Constraints

  • 16.1 Overview
  • 16.2 FX Logical Nodes Remain Distinct from Runtime Deployments
  • 16.3 FX Logical Endpoints Remain Distinct from Communication Technologies
  • 16.4 FX Logical Data Structures Remain Distinct from Serialisation Formats
  • 16.5 FX Runtime Planes Remain Distinct from Implementation Groupings
  • 16.6 FX Logical Interactions Remain Traceable
  • 16.7 FX Demo Logical Profile Does Not Prescribe Deployment Topology
  • 16.8 FX Demo Logical Profile Does Not Prescribe Communication Pattern Implementation
  • 16.9 FX Demo Logical Profile Does Not Prescribe Governance Tooling
  • 16.10 FX Demo Logical Constraints Summary
• 17. FX Demo Logical Requirements

  • 17.1 Overview
  • 17.2 FX Domain Profile Requirements
  • 17.3 FX Logical Node Requirements
  • 17.4 FX Logical Node Role Requirements
  • 17.5 FX Logical Communication Requirements
  • 17.6 FX Logical Information Requirements
  • 17.7 FX Runtime Plane Requirements
  • 17.8 FX Lifecycle Requirements
  • 17.9 FX Logical Interaction Requirements
  • 17.10 FX Logical Governance Requirements
  • 17.11 FX Logical Traceability Requirements
  • 17.12 Implementation Boundary Requirements

This document should be maintained as a set of linked wiki pages rather than a single monolithic page. Each major section should have its own stable URI so it can be referenced from other wiki pages, exported documents, presentations, AI-assisted tools, and semantic models.

Do not rename pages once they have been cited externally unless a redirect or move plan is in place.