====== 16.5 FX Runtime Planes Remain Distinct from Implementation Groupings ======
[[fxdemo:03-part:16-fx-demo-logical-rules-and-constraints:start | Go To FX Demo Logical Rules and Constraints ]]

An FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] classifies FX logical interactions by architectural purpose. It does not represent a [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Domain, DDS partition, DDS Topic namespace, [[dido:99_annexes:annex-b-terms-and-definitions:r:rest|REST]] resource group, [[dido:99_annexes:annex-b-terms-and-definitions:r:rpc|RPC]] service group, message-bus namespace, Kubernetes namespace, network segment, security zone, deployment environment, or runtime configuration grouping.

Implementation and deployment profiles select grouping mechanisms that help realise FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] separation. Those mechanisms support implementation or deployment, but they do not redefine the FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]].

FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] separation continues to apply when a single implementation mechanism handles interactions from multiple planes, or when multiple implementation mechanisms realise a single FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]].

----

<WRAP centeralign>

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

</WRAP>