3.4 Coverage of the Original FX Demo Reference Architecture [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 3.4 Coverage of the Original FX Demo Reference Architecture ======
[[fxdemo:02-part:start | Go To Top ]]

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 [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|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 [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].

Table 3-4:	Original FX Demo Reference Architecture material normalized 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 [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]] and logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_responsibility|responsibility assignments]]. |
| Communication Endpoint material | Generalised into logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]] and interaction roles. |
| Topic Framework | Generalised into logical endpoint and information-flow patterns. |
| Data Structure Framework | Generalised into logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Data Structure Definitions]] and logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_instance|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 [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_policy_constraints|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 [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | Deferred to Part 5: Phase 0 Deployment, Testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] Plan. |

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>