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

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 [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 [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== FX Contract State ======
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +FX Contract State represents the logical lifecycle condition of an FX [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]] or [[dido:99_annexes:annex-b-terms-and-definitions:t:transaction|Transaction]] as determined by the FX Demo logical profile.
 +
 +FX Contract State identifies the applicable state, state-transition context, prior state where applicable, triggering information, rule context, producing FX logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], timestamp, and provenance reference.
 +
 +FX Contract State participates primarily in the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]]. It also supports the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] because state transitions require lineage, reviewability, replay support, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] expectations.
 +
 +===== Definition =====
 +
 +//lifecycle condition of an FX [[dido:99_annexes:annex-b-terms-and-definitions:c:contract|Contract]] or [[dido:99_annexes:annex-b-terms-and-definitions:t:transaction|Transaction]]//
 +
 +===== Source =====
 +
 +Specialization of Logical Record from [[fxdemo:02-part:start]], Section 8.9, 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 the FX contract lifecycle and state material in the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
 +
 +===== Note =====
 +
 +FX Contract State is not a database status field, workflow state, implementation enum, state-machine implementation, event-store record, or persistence mechanism.
 +
 +===== Example =====
 +
 +FX Contract State records that a validated and semantically interpreted FX transaction has entered an accepted logical contract state.