FX Contract State Endpoint

Go up to Terms and Definitions

Discussion

The FX Contract State Endpoint carries FX Contract state information from the FX Contract State Node to downstream FX logical Nodes.

The endpoint supports contract lifecycle management, cash-flow computation, policy evaluation, audit, provenance, replay, reconstruction, and evidence expectations. It carries FX Contract State information that identifies the applicable state, state-transition context, input references, rule context, producing Node, timestamp, and provenance reference.

The FX Contract State Endpoint participates primarily in the FX Logical Data Plane. It also relates to the FX Logical Audit and Provenance Plane because contract state and state transitions require lineage and reviewability.

Definition

Communication Endpoint carrying state information for an FX Contract

Source

Specialization of Logical Communication Endpoint from Part 2: Distributed Node-Based Logical Architecture, Section 7.2, Logical Information Lineage from Part 2: Distributed Node-Based Logical Architecture, Section 8.10, and Traceability from Part 1: Conceptual Architecture, Section 7.10; generalised from contract lifecycle and state material in the original FX Demo Reference Architecture.

Note

The FX Contract State Endpoint is not a state-machine implementation, a database table, an event store, a workflow engine, a DDS Topic, a REST resource, or a deployment artifact.

Example

The FX Contract State Node publishes FX Contract State information that the FX Cash-Flow Computation Node consumes.