13.5 Runtime Plane Requirements
This section identifies the normative requirements for runtime planes established by Part 1. The canonical requirement statements are maintained in Annex C: Requirements, Part 1.
Table 13.5-1: Part 1 runtime plane requirements.
| Requirement ID | Statement |
|---|---|
| P1-REQ-13-5-001 |
The Conceptual Architecture SHALL define the following conceptual Runtime Planes: Control Plane, Data Plane, Health and Observability Plane, Policy and Release Plane, and Audit and Provenance Plane. |
| P1-REQ-13-5-002 |
The Control Plane SHALL support operational coordination among Nodes. |
| P1-REQ-13-5-003 |
The Data Plane SHALL carry Domain and analytical information among Nodes. |
| P1-REQ-13-5-004 |
The Health and Observability Plane SHALL support observation of operational condition and behavior. |
| P1-REQ-13-5-005 |
The Policy and Release Plane SHALL support governed access, disclosure, safeguarding, and release of information. |
| P1-REQ-13-5-006 |
The Audit and Provenance Plane SHALL support auditability, provenance, lineage, reconstruction, and defensibility. |
| P1-REQ-13-5-007 |
The Conceptual Architecture SHALL distinguish Runtime Planes from implementation mechanisms. |
| P1-REQ-13-5-008 |
The Conceptual Architecture SHALL NOT treat a Runtime Plane as a DDS Domain, DDS Topic, DDS partition, Kubernetes namespace, network segment, container group, security zone, or deployment environment. |
| P1-REQ-13-5-009 |
Cross-plane relationships SHALL preserve the distinct architectural purpose of each Runtime Plane involved. |
| P1-REQ-13-5-010 |
Cross-plane relationships SHALL be Traceable when they affect Governance and Authority, release, recovery, auditability, provenance, or Evidence. |
| P1-REQ-13-5-011 |
The Policy and Release Plane SHALL support conceptual separation between full transaction detail, transaction metadata, aggregate summaries, derived indicators, redacted views, masked views, exception views, and full-detail release views. |
| P1-REQ-13-5-012 |
The Policy and Release Plane SHALL support data sovereignty and data residency as conceptual release and movement concerns. |
| P1-REQ-13-5-013 |
The Policy and Release Plane SHALL support policy-governed release without requiring all protected information to pass through a single central policy mechanism. |
| P1-REQ-13-5-014 |
The Policy and Release Plane SHALL support later logical realization through policy enforcement, policy decision, policy administration, policy information, obligation, release, and audit/evidence capabilities. |
| P1-REQ-13-5-015 |
The Policy and Release Plane SHALL NOT treat metadata release or aggregate release as authorization to release full transaction detail. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.