====== FX Runtime Plane Traceability ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]

===== Discussion =====

FX Runtime Plane Traceability relates an FX logical interaction or information exchange to the FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] that frames its architectural purpose.

FX Runtime Plane Traceability helps reviewers distinguish operational coordination, FX domain information exchange, health reporting, policy and release, audit and provenance, replay, reconstruction, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] concerns. It also supports cross-plane review by identifying when one FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] affects, constrains, records, or produces information for another plane.

FX Runtime Plane Traceability preserves the separation of concerns even when a single FX logical interaction spans multiple planes.

===== Definition =====

//Traceability relationship connecting FX logical interactions and information exchanges to their FX Runtime Plane classification.//

===== Source =====

Specialisation of [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_runtime_plane_traceability|Logical Runtime Plane Traceability]] from Part 2, Section 12.6, Logical Runtime Plane Model from Part 2, Section 9, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] from Part 1, Section 7.5, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from Part 1, Section 7.10; generalised from FX runtime-plane and cross-plane material in the original FX Demo Reference Architecture.

===== Note =====

FX Runtime Plane Traceability does not prescribe [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] partitions, topic namespaces, Kubernetes namespaces, network segments, security zones, or implementation groupings.

===== Example =====

An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_node_status|FX Node Status]] report traces to the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]]. A recovery command triggered by that status report traces to the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]]. The relationship between those interactions identifies the cross-plane trace.

----

<WRAP centeralign>

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

</WRAP>