Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:f:fx_cash-flow_obligation_endpoint [2026/08/04 07:08] – ↷ Links adapted because of a move operation nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:f:fx_cash-flow_obligation_endpoint [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 7: / Line 7: @@
 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 [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|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 [[dido:99_annexes:annex-b-terms-and-definitions:n:financial_node|Node]], timestamp, and provenance reference.
+The endpoint supports analytical processing, policy evaluation, audit, provenance, oversight preparation, replay, reconstruction, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|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 [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], timestamp, and provenance reference.
 The FX Cash-Flow Obligation Endpoint participates primarily in the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]]. It also relates to the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] because computed obligations require [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to input contract state, semantic assertions, model references, calculation context, and the producing Node.