FX Contract State Transition

Return to Terms and Definitions

FX Contract State Transitions identify the allowed logical movement from one FX Contract State to another.

An FX Contract State Transition records the prior state, target state, triggering information, responsible FX logical Node or Node Role, applicable rule or interpretation context, timestamp, and provenance reference.

FX Contract State Transitions support review because they explain why a contract state changed and which inputs, rules, semantic assertions, validation results, or control interactions supported the change.

The FX Demo Logical Profile treats state transitions as logical relationships. It does not prescribe a state-machine engine, workflow engine, rules engine, database update, event-store mechanism, or orchestration mechanism.

Logical movement from one FX Contract State to another with recorded trigger, context, responsibility, and provenance.

Specialization of FX Contract State from Section 9.6, Contract State Management Role from Section 7.5, Logical Information Lineage from Part 2, Section 8.10, and Traceability from Part 1, Section 7.10; generalised from FX contract lifecycle and state-transition material in the original FX Demo Reference Architecture.

An FX Contract State Transition concerns the FX Contract State. It does not identify deployment state, process state, Node lifecycle state, or orchestration state.

An FX Contract State Transition moves a validated and semantically interpreted transaction into an accepted FX Contract State after the FX Contract State Node applies the applicable transition rule.