====== 20.2 Implementation Artefacts Do Not Redefine Logical Elements ======

[[fxdemo:04-part:start | Go To Top ]]

[[fxdemo:04-part:20-phase-0-implementation-rules-and-constraints:start | Return to Phase 0 Implementation Rules and Constraints ]]

Implementation artefacts realise logical elements. They do not redefine logical elements.

An implementation [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] module realises an FX logical Node or selected [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]]. A [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topic realises an FX logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]]. An [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] structure realises an FX logical information structure. A generated type realises an implementation representation of an IDL structure. A script supports generation, build preparation, execution, shutdown, cleanup, or [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflow]] activity.

None of these artefacts changes the meaning of the FX logical element it realises or supports. The Part 3 FX Demo Logical Profile remains the authoritative source for FX logical meaning.

<WRAP centeralign>

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

</WRAP>