12.13 FX Logical Interaction Pattern Summary
Go To FX Demo Logical Interaction Patterns
The FX Demo Logical Interaction Patterns define reusable platform-independent behavior for the FX Demo Logical Profile.
Table 12-12: Summary of FX Demo Logical Interaction Patterns.
| Pattern | Primary logical purpose | Primary Runtime Plane |
|---|---|---|
| Register FX Logical Node | Announce identity, roles, capabilities, endpoints, versions, and compatibility information | Logical Control Plane |
| Report FX Node Status | Report lifecycle state, health, availability, degradation, failure, or recovery progress | Logical Health and Observability Plane |
| Intake FX Transaction Candidate | Introduce candidate FX transaction information into the logical node network | Logical Data Plane |
| Validate FX Transaction Candidate | Validate candidate FX transaction information against logical validation expectations | Logical Data Plane |
| Interpret FX Transaction Semantics | Apply governed semantic context to validated FX transaction information | Logical Data Plane |
| Establish or Update FX Contract State | Determine and publish the FX Contract State | Logical Data Plane |
| Compute FX Cash-Flow Obligations | Compute projected or derived FX Cash-Flow Obligations | Logical Data Plane |
| Request FX Policy Decision | Evaluate release or handling constraints for FX information | Logical Policy and Release Plane |
| Release FX Information to Oversight Participant | Prepare authorized FX information for external oversight consumption | Logical Policy and Release Plane |
| Record FX Audit and Provenance | Preserve audit, provenance, lineage, reconstruction, and review information | Logical Audit and Provenance Plane |
| Replay or Reconstruct FX Information | Reproduce or reconstruct selected FX information from preserved records | Logical Audit and Provenance Plane |
These patterns define the core FX logical interaction vocabulary used by this profile. Part 4 maps these patterns to implementation artifacts. Part 5 deploys, tests, observes, and provides Evidence for the selected implementation.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.