This is an old revision of the document!
3.4 Coverage of the Original FX Demo Reference Architecture
The original FX Demo Reference Architecture serves as the source material for the distributed, node-based Logical Architecture defined in this part. That earlier material combined conceptual, logical, FX-specific, implementation, deployment, and Evidence concerns. This document set separates those concerns across Parts 1 through 5.
This part generalises the reusable Logical Architecture material from the original FX Demo Reference Architecture. It does not carry forward FX-specific transaction details, DDS bindings, IDL structures, QoS profiles, Python implementation patterns, Kubernetes deployment details, Crucible scenarios, scripts, or runtime Evidence.
Table 3-4: Original FX Demo Reference Architecture material normalised into Part 2
| Original FX Demo Reference Architecture material | Part 2: Logical treatment |
|---|---|
| Node relationships and responsibilities | Generalised into the Logical Node Model. |
| Node Role Framework | Generalised into logical Node Roles and logical responsibility assignments. |
| Communication Endpoint material | Generalised into logical Communication Endpoints and interaction roles. |
| Topic Framework | Generalised into logical endpoint and information-flow patterns. |
| Data Structure Framework | Generalised into logical Data Structure Definitions and logical Data Structure Instances. |
| Runtime Plane Model | Generalised into logical Runtime Planes and cross-plane relationships. |
| Control-plane status and command material | Generalised into logical control interactions. |
| Data-plane publication and subscription material | Generalised into logical information exchange patterns. |
| Policy and release material | Generalised into logical policy and release interactions. |
| Audit, provenance, persistence, and replay material | Generalised into logical traceability, audit, provenance, replay, and evidence-support relationships. |
| FX interaction sequences and use cases | Deferred to Part 3: FX Demo Logical Profile. |
| DDS, IDL, QoS, Python, and implementation mappings | Deferred to Part 4: Phase 0 Implementation Profile / PSM. |
| Kubernetes, K3S, Crucible, acceptance checks, and runtime Evidence | Deferred to Part 5: Phase 0 Deployment, Testability, and Evidence Plan. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.