====== 10.7 Cross-Plane Relationships in the FX Demo ======
[[fxdemo:03-part:10-fx-demo-runtime-plane-model:start | Go To FX Demo Runtime Plane Model ]]

Cross-plane relationships occur when an FX logical interaction in one [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] affects, references, constrains, or produces information in another [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]].

The FX Demo Runtime Plane Model preserves separation among planes while supporting explicit cross-plane relationships. The FX Demo Logical Profile records those relationships so reviewers understand how operational coordination, FX domain information exchange, health reporting, release control, audit, provenance, replay, reconstruction, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] support one another.

<WRAP table-caption>
**Table 10-1:** Examples of cross-plane relationships in the FX Demo.
</WRAP>

^ Originating FX Runtime Plane ^ Related FX Runtime Plane ^ Example ^
| [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]] | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]] | An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_node_status|FX Node Status]] report showing **Degraded** triggers an [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_control_command|FX Control Command]]. |
| [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]] | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] | An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_replay_request|FX Replay Request]] causes selected FX Data Plane information to be republished or reconstructed. |
| [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_policy_and_release_plane|Logical Policy and Release Plane]] | An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_cash-flow_obligation|FX Cash-Flow Obligation]] requires release evaluation before external disclosure. |
| [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_policy_and_release_plane|Logical Policy and Release Plane]] | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]] | An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_decision|FX Policy Decision]] creates an [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_audit_record|FX Audit Record]] and an [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_provenance_record|FX Provenance Record]]. |
| [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]] | An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_result|FX Validation Result]] creates provenance linking the input transaction, validation rule version, producing [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]], and the output. |
| [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]] | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] | An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_replay_result|FX Replay Result]] reconstructs selected FX domain information from preserved provenance and audit records. |

Cross-plane relationships do not collapse the planes into one another. Each [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] retains its architectural purpose. The relationship identifies how one plane affects, constrains, records, or supports another.

----

<WRAP centeralign>

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

</WRAP>