FX Runtime Plane Traceability

Return to Terms and Definitions

Discussion

FX Runtime Plane Traceability relates an FX logical interaction or information exchange to the FX 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 Evidence concerns. It also supports cross-plane review by identifying when one FX 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 Logical Runtime Plane Traceability from Part 2, Section 12.6, Logical Runtime Plane Model from Part 2, Section 9, Runtime Plane from Part 1, Section 7.5, and 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 DDS partitions, topic namespaces, Kubernetes namespaces, network segments, security zones, or implementation groupings.

Example

An FX Node Status report traces to the Logical Health and Observability Plane. A recovery command triggered by that status report traces to the Logical Control Plane. The relationship between those interactions identifies the cross-plane trace.

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