====== 8.2 Node Mapping Principles ======

[[fxdemo:04-part:08-mapping-from-fx-logical-nodes-to-implementation-artifacts:start | Go To Mapping from FX Logical Nodes to Implementation Artifacts ]]

The Phase 0 Implementation Profile applies the following principles when mapping FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]] to implementation artifacts.

Each implementation Node artifact identifies:

  * the FX logical Node or Nodes it realizes;
  * the FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Role]] or Node Roles it performs;
  * the [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] or Runtime Planes it supports;
  * the [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topics, [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] structures, generated types, configuration artifacts, scripts, and supporting modules it uses;
  * the relevant Part 3 FX logical Node definition;
  * the applicable Phase 0 Developer Handbook rules; and
  * the observable behavior required by the Phase 0 logging and exception-handling baseline.

The mapping does not require one-to-one correspondence between logical Nodes and runtime artifacts. A single runtime artifact may realize multiple FX logical Nodes. Multiple implementation artifacts may realize one FX logical Node. The mapping table records the selected Phase 0 choice.

----

<WRAP centeralign>

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

</WRAP>