FX Cash-Flow Obligation Endpoint

Go up to Terms and Definitions

Discussion

The FX Cash-Flow Obligation Endpoint carries projected or derived FX cash-flow obligation information from the FX Cash-Flow Computation Node to downstream FX logical Nodes.

The endpoint supports analytical processing, policy evaluation, audit, provenance, oversight preparation, replay, reconstruction, and evidence expectations. It carries FX Cash-Flow Obligation information that identifies obligation amount, currency, payment date, payer, receiver, contract reference, calculation context, model version, producing Node, timestamp, and provenance reference.

The FX Cash-Flow Obligation Endpoint participates primarily in the FX Logical Data Plane. It also relates to the FX Logical Audit and Provenance Plane because computed obligations require traceability to input contract state, semantic assertions, model references, calculation context, and the producing Node.

Definition

Communication Endpoint carrying projected or derived FX cash-flow obligation information

Source

Specialization of Logical Communication Endpoint from Part 2: Distributed Node-Based Logical Architecture, Section 7.2, Logical Assertion from Part 2: Distributed Node-Based Logical Architecture, Section 8.8, and Interpretation from Part 1: Conceptual Architecture, Section 9.5; generalised from ACTUS cash-flow and analytical computation material in the original FX Demo Reference Architecture.

Note

The FX Cash-Flow Obligation Endpoint does not prescribe the ACTUS library, calculation engine, DDS Topic, REST resource, RPC method, message queue, event stream, database table, or deployment artifact.

Example

The FX Cash-Flow Computation Node publishes FX Cash-Flow Obligations that the FX Policy and Release Node and the FX Audit and Provenance Node consume.