Differences

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

--- fxdemo:02-part:04-logical-architecture-principles:04-4-logical-separation-of-runtime-planes:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:02-part:04-logical-architecture-principles:04-4-logical-separation-of-runtime-planes:start [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 2: / Line 2: @@
 [[fxdemo:02-part:start | Go To Top ]]
-The Logical Architecture preserves the [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] separation defined in Part 1.
+The Logical Architecture preserves the [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] separation defined in Part 1.
-Logical interactions belong to logical Runtime Planes such as the [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Control Plane]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Data Plane]], [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Health and Observability Plane]], Policy and Release Plane, and Audit and Provenance Plane. This separation allows reviewers to understand the architectural purpose of each interaction before later parts select specific implementation mechanisms.
+Logical interactions belong to logical Runtime Planes such as the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Control Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Data Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Health and Observability Plane]], Policy and Release Plane, and Audit and Provenance Plane. This separation allows reviewers to understand the architectural purpose of each interaction before later parts select specific implementation mechanisms.
 Examples of cross-plane interactions include a health observation triggering a control action, a data-plane result requiring a policy decision, and a policy decision creating an audit and provenance record. These relationships connect planes without collapsing them into one another.