Cross-plane logical relationships occur when an interaction in one Logical Runtime Plane affects, references, constrains, or produces information in another Logical Runtime Plane.
The Logical Runtime Plane Model preserves separation among planes while allowing explicit cross-plane relationships. The Logical Architecture records those relationships so reviewers understand how operational coordination, domain information exchange, health reporting, release control, audit, provenance, and Evidence support one another.
Examples of cross-plane logical relationships include:
Table 9-1: Examples of cross-plane logical relationships
| Originating logical plane | Related logical plane | Example |
|---|---|---|
| Logical Health and Observability Plane | Logical Control Plane | A degraded-status event triggers a recovery command. |
| Logical Control Plane | Logical Data Plane | A replay command causes a Logical Node to republish selected Data Plane information. |
| Logical Data Plane | Logical Policy and Release Plane | A validation result requires an evaluation by the release before external disclosure. |
| Logical Policy and Release Plane | Logical Audit and Provenance Plane | A release decision creates an audit and provenance record. |
| Logical Data Plane | Logical Audit and Provenance Plane | A validation assertion creates provenance linking the inputs, the rule version, the producing Logical Node, and the output. |
Cross-plane logical relationships do not collapse the planes into one another. Each plane retains its architectural purpose. The relationship identifies how one plane affects or supports another.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.