====== 16.6 Logical Runtime Plane Requirements ======
[[fxdemo:02-part:16-logical-requirements:start | Go To Logical Requirements ]]

This section identifies the normative requirements established for the Logical Runtime Plane Model. The canonical requirement statements are maintained in [[dido:99_annexes:annex-d-requirements:part-02:start|Annex C: Requirements, Part 2, Section 16.6]].

<WRAP table-caption>
**Table 16-5:** Logical Runtime Plane requirements.
</WRAP>

^ Requirement ID ^ Statement ^
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-001|P2-REQ-16-6-001]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-001#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-002|P2-REQ-16-6-002]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-002#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-003|P2-REQ-16-6-003]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-003#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-004|P2-REQ-16-6-004]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-004#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-005|P2-REQ-16-6-005]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-005#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-006|P2-REQ-16-6-006]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-006#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-007|P2-REQ-16-6-007]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-007#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-008|P2-REQ-16-6-008]] | {{section>fxdemo:99_part_annexes:annex-c-requirements:part-02:p2-req-16-6-008#statement&noheader&


----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>