====== P4-REQ-21-8-006 ======

[[dido:99_annexes:annex-d-requirements:part-04:start| Return to Requirements]]

===== Statement =====

Each interaction realization SHALL identify the Runtime Plane or Runtime Planes involved.

===== Source =====

Part 4, Section 21.8: Interaction Pattern Realization Requirements.

===== Rationale =====

Runtime Plane identification preserves the separation of architectural concerns represented within each implementation interaction.

An interaction may cross multiple Runtime Planes, but each plane's purpose must remain identifiable so that communication, control, observation, policy, audit, and provenance concerns do not become conflated.

===== Applies To =====

This requirement applies to:

  * interaction realizations;
  * Runtime Plane mappings;
  * DDS Topic mappings;
  * participating implementation artifacts; and
  * cross-plane interactions.

===== Verification =====

Verification SHALL confirm that each interaction realization identifies all applicable Runtime Planes.

Verification activities should include review checks confirming that:

  * applicable Runtime Planes are explicitly identified;
  * cross-plane interactions identify each plane involved;
  * implementation behavior remains consistent with plane purpose; and
  * Runtime Plane distinctions remain reviewable.

===== Traceability =====

This requirement connects interaction realizations to the Runtime Plane classifications defined by the FX Demo Logical Profile.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-7-001]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-7-007]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-8-009]]

Related source section:

  * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-8-interaction-pattern-realization-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>

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

</WRAP>