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/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state_endpoint to dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state_endpoint nick_dido
+++ 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 1: / Line 1: @@
 ====== FX Contract State Endpoint ======
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 ===== Discussion =====
-The FX Contract State Endpoint carries FX [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]] state information from the FX Contract State Node to downstream FX logical Nodes.
+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: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: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:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]]. It also relates to the FX Logical [[dido:99_annexes: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.
+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.
 ===== Definition =====
-//[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] carrying state information for an FX [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]]//
+//[[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] carrying state information for an FX [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]]//
 ===== Source =====
-Specialisation of Logical Communication Endpoint from [[fxdemo:02-part:start]], Section 7.2, Logical Information Lineage from [[fxdemo:02-part:start]], Section 8.10, and [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from [[fxdemo:01-part:start]], Section 7.10; generalised from contract lifecycle and state material in the original FX Demo [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
+Specialization of Logical Communication Endpoint from [[fxdemo:02-part:start]], Section 7.2, Logical Information Lineage from [[fxdemo:02-part:start]], Section 8.10, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from [[fxdemo:01-part:start]], Section 7.10; generalised from contract lifecycle and state material in the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|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 artefact.
+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 =====