====== 16.10 FX Demo Logical Constraints Summary ======
[[fxdemo:03-part:16-fx-demo-logical-rules-and-constraints:start | Go To FX Demo Logical Rules and Constraints ]]

The FX Demo Logical Profile applies the following constraints:

  * FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]] remain distinct from runtime deployments.
  * FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]] remain distinct from communication technologies.
  * FX logical information structures remain distinct from serialisation formats and implementation schemas.
  * FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]] remain distinct from implementation groupings.
  * FX logical interactions remain [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceable]].
  * The FX Demo Logical Profile does not prescribe deployment topology.
  * The FX Demo Logical Profile does not prescribe the implementation of communication patterns.
  * The FX Demo Logical Profile does not prescribe governance tooling.
  * Implementation Profiles / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSMs]] preserve the FX Demo Logical Profile while mapping FX logical elements to selected technologies.
  * Deployment, Testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] Plans preserve the FX Demo Logical Profile while deploying, testing, observing, and evidencing selected implementation artefacts.

----

<WRAP centeralign>

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

</WRAP>