20.12 Implementation Constraints Summary [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.12 Implementation Constraints Summary ======

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

The Phase 0 Implementation Profile applies the following constraints.

  - Implementation artefacts do not redefine logical elements
  - [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topics do not redefine FX logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]]
  - [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] structures do not redefine FX logical information structures
  - Generated types do not redefine FX logical information structures
  - Runtime processes do not redefine FX logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]]
  - [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] layout does not redefine architecture
  - Scripts do not redefine interaction patterns
  - The Developer Handbook does not replace the implementation profile
  - Phase 0 does not define later phase implementation profiles
  - [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]] and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] concerns remain outside Part 4

<WRAP centeralign>

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

</WRAP>