10.7 Cross-Plane Relationships in the FX Demo
Go To FX Demo Runtime Plane Model
Cross-plane relationships occur when an FX logical interaction in one Runtime Plane affects, references, constrains, or produces information in another 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 Evidence support one another.
Table 10-1: Examples of cross-plane relationships in the FX Demo.
| Originating FX Runtime Plane | Related FX Runtime Plane | Example |
|---|---|---|
| Logical Health and Observability Plane | Logical Control Plane | An FX Node Status report showing Degraded triggers an FX Control Command. |
| Logical Control Plane | Logical Data Plane | An FX Replay Request causes selected FX Data Plane information to be republished or reconstructed. |
| Logical Data Plane | Logical Policy and Release Plane | An FX Cash-Flow Obligation requires release evaluation before external disclosure. |
| Logical Policy and Release Plane | Logical Audit and Provenance Plane | An FX Policy Decision creates an FX Audit Record and an FX Provenance Record. |
| Logical Data Plane | Logical Audit and Provenance Plane | An FX Validation Result creates provenance linking the input transaction, validation rule version, producing Node, and the output. |
| Logical Audit and Provenance Plane | Logical Data Plane | An 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 Runtime Plane retains its architectural purpose. The relationship identifies how one plane affects, constrains, records, or supports another.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.