3.5 Coverage of the Original FX Demo Reference Architecture

Go To Top

The original FX Demo Reference Architecture serves as the source material for the FX Demo Logical Profile. The new document set does not discard that material. It places the FX-specific logical material in this part and defers implementation, deployment, testability, and runtime Evidence material to later parts.

This part carries forward FX-specific logical material from the original FX Demo Reference Architecture. It does not carry forward DDS bindings, IDL structures, QoS profiles, Python implementation patterns, Kubernetes deployment details, Crucible scenarios, scripts, or runtime Evidence.

Table 3-5: Original FX Demo Reference Architecture material normalised into Part 3.

Original FX Demo Reference Architecture material	Part 3 FX logical treatment
FX-specific use cases and interaction sequences	Normalised into FX logical interaction patterns.
FX-specific Node catalogue	Normalised into FX logical Nodes and Logical Node Roles.
FX transaction intake material	Normalised into the FX Transaction Intake Node, endpoint, information structures, and interaction patterns.
FX validation material	Normalised into FX Validation Node, FX Validation Result, validation endpoint, and validation interaction pattern.
FX semantic interpretation material	Normalised into the FX Semantic Interpretation Node, the FX Semantic Assertion, the semantic interpretation endpoint, and the interpretation pattern.
ACTUS cash-flow concerns	Normalised into FX Cash-Flow Computation Node, FX Cash-Flow Obligation, and cash-flow computation interaction pattern without binding to an ACTUS implementation library.
FX contract lifecycle material	Normalised into FX Contract State, lifecycle states, state transitions, and contract-state interaction patterns.
IEF policy and release material	Normalised into FX Policy and Release Node, FX Policy Decision, FX Release Package, and release-to-oversight interaction pattern.
Audit, provenance, persistence, and replay material	Normalised into FX Audit and Provenance Node, FX Audit Record, FX Provenance Record, replay and reconstruction patterns, and Evidence expectations.
DDS, IDL, QoS, Python, and implementation mappings	Deferred to Part 4: Phase 0 Implementation Profile / Platform Specific Model (PSM).
Kubernetes, K3s, Crucible, acceptance checks, deployment, and runtime Evidence	Deferred to Part 5: Phase 0 Deployment, Testability, and Evidence Plan.
Scripts and repository layout	Deferred to supporting repository documentation or the developer handbook.

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