====== 4.6 Runtime Plane Separation in the FX Demo ====== [[fxdemo:03-part:04-fx-demo-logical-profile-principles:start | Go To FX Demo Logical Profile Principles ]] The FX Demo Logical Profile preserves [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] separation within the [[dido:99_annexes:annex-b-terms-and-definitions:f:foreign_exchange_domain|Foreign Exchange Domain]]. FX [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]] interactions coordinate operational behavior. FX [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] interactions carry FX domain and analytical information. FX [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]] interactions report the FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] condition. FX [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_policy_and_release_plane|Logical Policy and Release Plane]] interactions govern access, disclosure, safeguarding, and release. FX [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]] interactions preserve reconstruction, lineage, accountability, and defensibility. Cross-plane relationships connect these concerns without collapsing them. A health observation triggers control action. An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_result|FX Validation Result]] requires release evaluation before external disclosure. A release decision creates [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_audit_record|FX Audit Record]] and [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_provenance_record|FX Provenance Record]]. An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_replay_request|FX Replay Request]] connects control, data, audit, and provenance concerns. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.