Differences

This shows you the differences between two versions of the page.

--- fxdemo:01-part:11-conceptual-rules-and-constraints:11-5-runtime-planes-remain-conceptual-classifications [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:11-5-runtime-planes-remain-conceptual-classifications to fxdemo:01-part:11-conceptual-rules-and-constraints:11-5-runtime-planes-remain-conceptual-classifications owen
+++ fxdemo:01-part:11-conceptual-rules-and-constraints:11-5-runtime-planes-remain-conceptual-classifications [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 [[fxdemo:01-part:start | Go to Top ]]
-Runtime Planes classify communication and behaviour by architectural purpose. They do not prescribe implementation mechanisms.
+[[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]] classify communication and behavior by architectural purpose. They do not prescribe implementation mechanisms.
-A later implementation profile may realise Runtime Plane separation through DDS Topics, topic namespaces, partitions, APIs, queues, services, security policies, network segmentation, or deployment configuration. Those mechanisms support plane separation, but they do not define the Runtime Plane.
+A later implementation profile may realize [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] separation through DDS Topics, topic namespaces, partitions, APIs, queues, services, security policies, network segmentation, or deployment configuration. Those mechanisms support plane separation, but they do not define the [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]].
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>