====== 4.5 Relationship to the FX Demo Logical Profile ======

[[fxdemo:04-part:04-phase-0-implementation-profile-overview:start | Go To Phase 0 Implementation Profile Overview ]]

The Phase 0 Implementation Profile maps selected elements of the Part 3 FX Demo Logical Profile to Phase 0 implementation artifacts.

Part 3 remains the authoritative source for the logical meaning of the FX Demo. It defines FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]], logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], logical information structures, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], interaction patterns, governance relationships, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] relationships, and logical requirements.

Part 4 does not redefine those logical elements. It maps them to implementation artifacts. A [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topic realizes an FX logical Communication Endpoint. An [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] structure realizes an FX logical information structure. A generated type realizes a selected implementation representation of that information structure. An implementation Node realizes an FX logical Node or selected Node Role. A script supports build or execution activity; it does not redefine the logical interaction pattern.

This relationship protects the distinction between the logical architecture and the implementation profile. The implementation profile provides the selected Phase 0 realization of the logical profile without changing it.

----

<WRAP centeralign>

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

</WRAP>