dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state_node

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state_node [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state_node [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== FX Contract State Node ======
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +The FX Contract State Node establishes, updates, and reports state information for an FX [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]] at the logical level.
 +
 +The FX Contract State Node performs contract state management responsibilities. It consumes validated and semantically interpreted FX transaction information, determines the applicable FX Contract State, applies allowed state transitions, records transition context, and publishes contract state information for downstream processing, cash-flow computation, audit, provenance, and oversight.
 +
 +The FX Contract State Node participates primarily in the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]]. It also participates in the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] when it records state-transition provenance.
 +
 +===== Definition =====
 +
 +//responsible for establishing, updating, and reporting state information for an FX [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]]//
 +
 +===== Source =====
 +
 +Specialization of Logical Node from [[fxdemo:02-part:start]], Section 6.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 Node defines the logic for state management. It does not prescribe a state-machine implementation, a database table, a workflow engine, an event store, or a persistence mechanism.
 +
 +===== Example =====
 +
 +The FX Contract State Node records that a validated FX transaction has moved into an accepted logical contract state and publishes the resulting FX Contract State.
 +
 +----
 +
 +<WRAP centeralign>
 +
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +</WRAP>