17.5 FX Logical Communication Requirements

Go To FX Demo Logical Requirements

This section identifies the normative requirements established for FX logical Communication Endpoints within the FX Demo Logical Profile. The canonical requirement statements are maintained in Annex D: Requirements, Part 3, Section 17.5.

Table 17-4: FX logical Communication Endpoint requirements.

Requirement ID Statement
P3-REQ-17-5-001

The FX Demo Logical Profile SHALL define FX logical Communication Endpoints.

P3-REQ-17-5-002

The FX Demo Logical Profile SHALL define the following FX logical Communication Endpoints:

  • FX Transaction Intake Endpoint
  • FX Validation Result Endpoint
  • FX Semantic Interpretation Endpoint
  • FX Contract State Endpoint
  • FX Cash-Flow Obligation Endpoint
  • FX Policy Decision Endpoint
  • FX Release Package Endpoint
  • FX Audit Record Endpoint
  • FX Provenance Record Endpoint
  • FX Node Status Endpoint
  • FX Control Command Endpoint
  • FX Replay Request Endpoint
  • FX Replay Result Endpoint
P3-REQ-17-5-003

Each FX logical Communication Endpoint SHALL specialise Logical Communication Endpoint from Part 2.

P3-REQ-17-5-004

Each FX logical Communication Endpoint SHALL preserve traceability to the Communication Endpoint from Part 1.

P3-REQ-17-5-005

Each FX logical Communication Endpoint SHALL identify participating FX logical Nodes or Node Roles, communication roles, carried FX logical information structures, Runtime Plane classification, governance constraints, traceability relationships, and evidence expectations.

P3-REQ-17-5-006

The FX Demo Logical Profile SHALL distinguish FX logical Communication Endpoints from DDS Topics, REST resources, RPC methods, Protocol Buffers services, message queues, event streams, files, database handoffs, shared-memory locations, network routes, and deployment artefacts.

P3-REQ-17-5-007

The FX Demo Logical Profile SHALL NOT prescribe one communication technology or interaction style.


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.