dido:99_annexes:annex-b-terms-and-definitions:l:logical_runtime_plane_traceability

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:l:logical_runtime_plane_traceability [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:l:logical_runtime_plane_traceability [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Logical Runtime Plane Traceability ======
  
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]]
 +
 +===== Discussion =====
 +
 +Logical Runtime Plane Traceability relates a logical interaction to the Runtime Plane that frames its architectural purpose.
 +
 +Logical Runtime Plane Traceability helps reviewers distinguish control, data, health and observability, policy, release, and audit and provenance concerns. It also supports cross-plane review by identifying when one plane affects, constrains, or produces information for another plane.
 +
 +Logical Runtime Plane Traceability preserves the separation of runtime concerns, even when an interaction spans multiple planes.
 +
 +===== Definition =====
 +
 +//Traceability relationship connecting logical interactions and information exchanges to their Logical Runtime Plane classification.//
 +
 +===== Source =====
 +
 +Specialization of Runtime Plane and Traceability from Part 1, Sections 7.5 and 7.10; generalised from runtime-plane and cross-plane material in the original FX Demo Reference Architecture.
 +
 +===== Note =====
 +
 +Logical Runtime Plane Traceability does not prescribe DDS partitions, topic namespaces, Kubernetes namespaces, network segments, security zones, or implementation groupings.
 +
 +===== Example =====
 +
 +A degraded-status event traces to the Logical Health and Observability Plane. A recovery command triggered by that event traces to the Logical Control Plane. The relationship between those interactions identifies the cross-plane trace.
 +
 +----
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]]
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>