Differences

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

--- fxdemo:01-part:08-conceptual-runtime-plane-model:08-1-overview [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:01-part:08-conceptual-runtime-plane-model:08-1-overview [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 [[fxdemo:01-part:start | Go to Top ]]
-The Conceptual [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] Model classifies runtime communication and behaviour by architectural purpose. It helps authors and reviewers distinguish operational coordination, [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]] information exchange, health reporting, policy-governed release, and audit/provenance activity before later parts map those concerns to technologies, deployment artefacts, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] packages.
+The Conceptual [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] Model classifies runtime communication and behavior by architectural purpose. It helps authors and reviewers distinguish operational coordination, [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]] information exchange, health reporting, policy-governed release, and audit/provenance activity before later parts map those concerns to technologies, deployment artifacts, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] packages.
-[[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]]s do not define implementation mechanisms. A later implementation profile may realise [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] separation through DDS Topics, topic namespaces, partitions, APIs, message queues, Kubernetes namespaces, security policies, network segmentation, configuration conventions, or other mechanisms. Those mechanisms may support plane separation, but they do not define the planes themselves.
+[[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]]s do not define implementation mechanisms. 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, message queues, Kubernetes namespaces, security policies, network segmentation, configuration conventions, or other mechanisms. Those mechanisms may support plane separation, but they do not define the planes themselves.
 Figure 8.1-1 identifies the conceptual Runtime Planes used by the Financial Systems Archetype.