Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state_endpoint [2026/07/18 12:33] – external edit 127.0.0.1
+++ dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state_endpoint [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 7: / Line 7: @@
 The FX Contract State Endpoint carries FX [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|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 [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] expectations. It carries FX Contract State information that identifies the applicable state, state-transition context, input references, rule context, producing [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], timestamp, and provenance reference.
+The endpoint supports contract lifecycle management, cash-flow computation, policy evaluation, audit, provenance, replay, reconstruction, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] expectations. It carries FX Contract State information that identifies the applicable state, state-transition context, input references, rule context, producing [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], timestamp, and provenance reference.
 The FX Contract State 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 contract state and state transitions require lineage and reviewability.