17.7 FX Runtime Plane Requirements
Go To FX Demo Logical Requirements
This section identifies the normative requirements established for FX Runtime Plane participation within the FX Demo Logical Profile. The canonical requirement statements are maintained in Annex D: Requirements, Part 3, Section 17.7.
Table 17-6: FX Runtime Plane requirements.
| Requirement ID | Statement |
|---|---|
| P3-REQ-17-7-001 |
The FX Demo Logical Profile SHALL define participation in the FX Runtime Plane. |
| P3-REQ-17-7-002 |
The FX Demo Logical Profile SHALL use the following FX Runtime Planes:
|
| P3-REQ-17-7-003 |
The Logical Control Plane SHALL support operational coordination among FX logical Nodes. |
| P3-REQ-17-7-004 |
The Logical Data Plane SHALL carry FX domain, analytical, lifecycle, validation, interpretation, and derived information among FX logical Nodes. |
| P3-REQ-17-7-005 |
The Logical Health and Observability Plane SHALL support observation of FX logical Node operational condition and behaviour. |
| P3-REQ-17-7-006 |
The Logical Policy and Release Plane SHALL support governed access, disclosure, safeguarding, redaction, transformation, marking, obligations, and release of FX information. |
| P3-REQ-17-7-007 |
The Logical Audit and Provenance Plane SHALL support auditability, provenance, lineage, reconstruction, replay, review, accountability, and defensibility for FX logical processing. |
| P3-REQ-17-7-008 |
The FX Demo Logical Profile SHALL distinguish FX Runtime Planes from DDS domains, DDS topics, DDS partitions, REST resource groups, RPC service groups, message queues, event streams, Kubernetes namespaces, network segments, security zones, deployment environments, and runtime configuration groupings. |
| P3-REQ-17-7-009 |
Cross-plane FX logical relationships SHALL preserve the distinct architectural purpose of each FX Runtime Plane involved. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.