20.6 Runtime Processes Do Not Redefine FX Logical Nodes [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.

====== 20.6 Runtime Processes Do Not Redefine FX Logical Nodes ======

[[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 ]]

A runtime process, module, service-like participant, process entry point, script-supported executable, or runtime participant may realise one or more FX logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] or [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Roles]].

Runtime packaging does not redefine FX logical Nodes. A single process may realise several FX logical Nodes. Several processes may realise one FX logical Node. A supporting module may assist several implementation participants. These choices remain implementation mappings. They do not change the logical Node definitions in Part 3.

The implementation profile must record the selected Phase 0 mapping so reviewers can [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Trace]] runtime artefacts back to the FX logical Nodes or Node Roles they realise.

<WRAP centeralign>

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

</WRAP>