dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-008:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-008:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-008:start [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P1-REQ-13-5-008 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The Conceptual Architecture SHALL NOT treat a [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] as a DDS Domain, DDS Topic, DDS partition, Kubernetes namespace, network segment, container group, security zone, or deployment environment.
 +
 +===== Source =====
 +
 +Part 1, Section 13.5: Runtime Plane Requirements.
 +
 +===== Rationale =====
 +
 +A Runtime Plane expresses architectural purpose. DDS Domains, DDS Topics, DDS partitions, Kubernetes namespaces, network segments, container groups, security zones, and deployment environments express implementation or deployment concerns.
 +
 +Treating a Runtime Plane as one of these mechanisms collapses conceptual runtime purpose into a selected technical or operational arrangement.
 +
 +===== Applies To =====
 +
 +This requirement applies to all Runtime Plane references within the Conceptual Architecture.
 +
 +It applies specifically to separation between Runtime Planes and:
 +
 +  * DDS Domains
 +  * DDS Topics
 +  * DDS partitions
 +  * Kubernetes namespaces
 +  * Network segments
 +  * Container groups
 +  * Security zones
 +  * Deployment environments
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Conceptual Architecture does not treat a Runtime Plane as an implementation or deployment mechanism.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Runtime Plane references identify architectural purpose
 +  * DDS constructs do not replace Runtime Plane concepts
 +  * Kubernetes constructs do not replace Runtime Plane concepts
 +  * Network and security boundaries do not replace Runtime Plane concepts
 +  * Deployment environments do not replace Runtime Plane concepts
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-5-runtime-plane-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-005:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>