dido:99_annexes:annex-b-terms-and-definitions:c:contract_state_management_role

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:c:contract_state_management_role [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:c:contract_state_management_role [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Contract State Management Role ======
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +The Contract State Management Role is responsible for establishing, updating, and reporting the FX contract state at the logical level.
 +
 +This role includes consuming validated and semantically interpreted FX transaction information, determining applicable FX Contract State, applying allowed state transitions, publishing contract state information, and preserving transition provenance.
 +
 +The Contract State Management Role 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]] when state transitions preserve input references, rule context, producing [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], timestamp, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] expectations.
 +
 +===== Definition =====
 +
 +//responsible for establishing, updating, and reporting FX contract state//
 +
 +===== Source =====
 +
 +Specialization of Logical Node Role from [[fxdemo:02-part:start]], Section 6.4, 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 Contract State Management Role does not prescribe a state-machine implementation, workflow engine, database table, event store, persistence mechanism, or orchestration tool.
 +
 +===== Example =====
 +
 +The FX Contract State Node performs the Contract State Management Role by determining and publishing the FX Contract State for a validated transaction.
 +
 +----
 +
 +<WRAP centeralign>
 +
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +</WRAP>