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 and Provenance State RecordCash-Flow Computation TriggerFX Contract State TransitionFX Endpoint TraceabilityFX Evidence TraceabilityFX Information Structure TraceabilityFX Interaction TraceabilityFX Logical Admission RulesFX Logical CompatibilityFX Logical Ownership of DefinitionsFX Logical Policy ConstraintsFX Logical VersioningFX Node TraceabilityFX Transaction Intake NodeFX Transaction Lifecycle StateFX Validation NodeLPart 1 Concept to FX Logical Profile ElementPart 1 Concept to FX Logical Profile ElementP2-REQ-16-2-003P2-REQ-16-2-004P2-REQ-16-3-001P2-REQ-16-3-002P2-REQ-16-3-003P2-REQ-16-3-004P2-REQ-16-3-005P2-REQ-16-3-006P2-REQ-16-3-007P2-REQ-16-3-008P2-REQ-16-3-009P2-REQ-16-4-003P2-REQ-16-4-004P2-REQ-16-6-002P2-REQ-16-6-003P2-REQ-16-7-003P2-REQ-16-9-004P2-REQ-16-9-005P2-REQ-16-9-006P2-REQ-16-9-0086.2 Logical Node7.1 Overview7.12 Communication Direction and Coupling8.1 Overview9.7 Cross-Plane Logical Relationships10.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 Summary11.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 Profiles14.1 Overview14.2 Logical Elements Prepared for Technology Mapping14.5 Execution and Deployment Independence14.6 Implementation Mapping Boundaries14.8 Boundary Between Part 2 and Implementation Profiles15.2 Logical Nodes Remain Distinct from Runtime Deployments15.3 Logical Endpoints Remain Distinct from Communication Technologies15.6 Logical Interactions Remain Traceable15.7 Logical Architecture Does Not Prescribe Deployment Topology15.10 Domain Profiles Preserve the Logical Architecture15.11 Implementation Profiles Preserve the Logical Architecture15.12 Logical Constraints Summary16.2 Distributed Node-Based Architecture Requirements16.3 Logical Node Requirements16.4 Logical Communication Requirements16.6 Logical Runtime Plane Requirements16.7 Logical Interaction Requirements16.9 Logical Traceability Requirements3.3 Traceability to Part 1 Conceptual Architecture3.4 Traceability to Part 2 Distributed Node-Based Logical Architecture / PIM3.5 Coverage of the Original FX Demo Reference Architecture3. Traceability to Parent and Source Architectures4.1 Domain Specialization without Conceptual Redefinition4.1 Domain Specialisation without Conceptual Redefinition4.3 Distributed FX Node Network4.4 Explicit FX Communication Endpoints4.6 Runtime Plane Separation in the FX Demo4.7 Traceability from Concept to Logical Profile4.8 Evidence-Oriented FX Logical Design5.1 Overview5.4 FX Demo Logical Node Network5.5 FX Demo Logical Communication Model5.6 FX Demo Logical Information Model5.7 FX Demo Logical Runtime Plane Model5.8 FX Demo Logical Traceability Model6.1 Overview6. FX Demo Logical Node Model7.1 Overview8.1 Overview9.1 Overview10.7 Cross-Plane Relationships in the FX Demo12.1 Overview12.2 Register FX Logical Node12.3 Report FX Node Status12.4 Intake FX Transaction Candidate12.5 Validate FX Transaction Candidate12.6 Interpret FX Transaction Semantics12.7 Establish or Update FX Contract State12.8 Compute FX Cash-Flow Obligations12.9 Request FX Policy Decision12.10 Release FX Information to Oversight Participant12.11 Record FX Audit and Provenance12.12 Replay or Reconstruct FX Information13.1 Overview15.1 Overview15.2 FX Logical Elements Prepared for Technology Mapping15.5 FX Execution and Deployment Independence15.6 Boundary Between Part 3 and Part 416.2 FX Logical Nodes Remain Distinct from Runtime Deployments16.3 FX Logical Endpoints Remain Distinct from Communication Technologies16.6 FX Logical Interactions Remain Traceable16.7 FX Demo Logical Profile Does Not Prescribe Deployment Topology16.10 FX Demo Logical Constraints Summary1. Scope2. Relationship to Parts 0, 1, 2, and 33.1 Traceability to SIP-RA3.3 Traceability to Part 1 Conceptual Architecture3.4 Traceability to Part 2 Distributed Node-Based Logical Architecture / Platform-Independent Model (PIM)3.5 Traceability to Part 3 FX Demo Logical Profile4.1 Overview4.2 Phase 0 Implementation Scope4.5 Relationship to the FX Demo Logical Profile4.6 Relationship to Later Development Phases5.2 Implementation Artifacts Realize Logical Elements6.2 Part 3 Working Baseline7.1 Overview7.6 Python as Phase 0 Implementation Language7.7 Scripts as Phase 0 Build and Execution Helpers8.1 Overview8.2 Node Mapping Principles8.3 Implementation Artifact Categories for Nodes8.4 FX Transaction Intake Node Mapping8.5 FX Validation Node Mapping8.6 FX Semantic Interpretation Node Mapping8.7 FX Contract State Node Mapping8.8 FX Cash-Flow Computation Node Mapping8.9 FX Policy and Release Node Mapping8.10 FX Audit and Provenance Node Mapping8.11 FX Health and Observability Node Mapping8.12 FX Registry and Coordination Node Mapping8.13 FX Replay and Reconstruction Node Mapping8.15 FX Logical Node Mapping Summary9.1 Overview9.2 Topic Mapping Principles10.2 Information Structure Mapping Principles10.15 FX Node Status Mapping10.16 FX Control Command Mapping dido/99_annexes/annex-b-terms-and-definitions/l/logical_node.txt Last modified: 2026/08/04 07:09by nick_dido