P3-REQ-17-5-002 [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== P3-REQ-17-5-002 ======

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

===== Statement =====

The FX Demo Logical Profile SHALL define the following FX logical Communication Endpoints:

  * FX Transaction Intake Endpoint
  * FX Validation Result Endpoint
  * FX Semantic Interpretation Endpoint
  * FX Contract State Endpoint
  * FX Cash-Flow Obligation Endpoint
  * FX Policy Decision Endpoint
  * FX Release Package Endpoint
  * FX Audit Record Endpoint
  * FX Provenance Record Endpoint
  * FX Node Status Endpoint
  * FX Control Command Endpoint
  * FX Replay Request Endpoint
  * FX Replay Result Endpoint

===== Source =====

Part 3, Section 17.5: FX Logical Communication Requirements.

===== Rationale =====

The identified FX logical Communication Endpoints define the standard logical communication interfaces required to support the Foreign Exchange Domain. Establishing a common set of logical Communication Endpoints provides a consistent architectural vocabulary for logical information exchange while enabling interoperability, governance, traceability, and architectural reuse.

By defining these logical Communication Endpoints independently of implementation technologies, the FX Demo Logical Profile allows multiple Implementation Profiles to realize the same logical communication architecture using different communication mechanisms while preserving architectural consistency.

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

This requirement applies to the definition, review, maintenance, and evolution of the FX Demo Logical Profile.

It applies specifically to:

  * FX logical Communication Endpoint definitions;
  * logical communication architecture;
  * architectural reviews;
  * Domain Logical Profiles; and
  * derived Implementation Profiles.

===== Verification =====

Verification SHALL confirm that every required FX logical Communication Endpoint is defined.

Verification activities should include review checks confirming that:

  * each required logical Communication Endpoint is present;
  * logical Communication Endpoint names are consistent with the architectural specification;
  * no required logical Communication Endpoint is omitted; and
  * each logical Communication Endpoint is uniquely identifiable.

===== Traceability =====

This requirement establishes the required logical Communication Endpoint inventory for the FX Demo Logical Profile.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-03:p3-req-17-5-001]]
  * [[dido:99_annexes:annex-d-requirements:part-03:p3-req-17-5-003]]
  * [[dido:99_annexes:annex-d-requirements:part-03:p3-req-17-5-004]]

Related source section:

  * [[fxdemo:03-part:17-fx-demo-logical-requirements:17-5-fx-logical-communication-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>

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

</WRAP>