P3-REQ-17-5-005

Each FX logical Communication Endpoint SHALL identify participating FX logical Nodes or Node Roles, communication roles, carried FX logical information structures, Runtime Plane classification, governance constraints, traceability relationships, and evidence expectations.

Part 3, Section 17.5: FX Logical Communication Requirements.

A logical Communication Endpoint represents more than a communication path between logical Nodes. It defines the architectural meaning of communication by identifying the participating logical Nodes or Node Roles, the information exchanged, the Runtime Plane in which communication occurs, the applicable governance constraints, the required traceability relationships, and the evidence expectations associated with the communication.

Capturing these characteristics allows Communication Endpoints to serve as complete architectural descriptions while remaining independent of any implementation technology or deployment environment.

This requirement applies to every FX logical Communication Endpoint defined by the FX Demo Logical Profile.

It applies specifically to:

  • logical Communication Endpoint definitions;
  • logical communication modeling;
  • Runtime Plane classification;
  • governance specification;
  • architectural traceability; and
  • evidence definition.

Verification SHALL confirm that each FX logical Communication Endpoint identifies all required architectural characteristics.

Verification activities should include review checks confirming that:

  • participating FX logical Nodes or Node Roles are identified;
  • communication roles are identified;
  • carried FX logical information structures are identified;
  • Runtime Plane classification is specified;
  • governance constraints are identified;
  • traceability relationships are documented; and
  • evidence expectations are identified.

This requirement establishes the complete architectural definition required for each FX logical Communication Endpoint within the FX Demo Logical Profile.

Related requirement identifiers:

Related source section:

Draft


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

  • dido/99_annexes/annex-d-requirements/part-03/p3-req-17-5-005.txt
  • Last modified: 2026/07/21 15:29
  • by owen