This is an old revision of the document!
FX Transaction Lifecycle State
Discussion
FX Transaction Lifecycle States identify the logical processing condition of FX transaction information as it moves through intake, validation, semantic interpretation, contract state processing, cash-flow computation, release evaluation, audit, provenance, replay, and reconstruction.
The FX Demo Logical Profile uses lifecycle states to support review, Traceability, governance, replay, and Evidence planning. Lifecycle states identify logical processing conditions; they do not prescribe implementation status fields, database columns, workflow states, event types, or runtime orchestration states.
FX Transaction Lifecycle States include:
-
Candidate;
-
Intake Recorded;
-
Validation Pending;
-
Validation Failed;
-
Validation Passed;
-
Semantic Interpretation Pending;
-
Semantically Interpreted;
-
Contract State Pending;
-
Contract State Established;
-
Cash-Flow Computation Pending;
-
Cash-Flow Computed;
-
Release Evaluation Pending;
-
Release Approved;
-
Release Denied;
-
Released;
-
Audited;
-
Provenance Recorded;
-
Replay Requested;
-
Reconstructed; and
-
Superseded.
A domain profile or implementation profile refines these states only when it preserves the logical meaning and Traceability defined here.
Definition
FX logical lifecycle condition associated with FX transaction information during processing, release, audit, provenance, replay, or reconstruction.
Source
Specialisation of Logical Data Structure Instance from Part 2, Section 8.3, Logical Record from Part 2, Section 8.9, Logical Information Lineage from Part 2, Section 8.10, and Traceability from Part 1, Section 7.10; generalised from FX transaction lifecycle and state material in the original FX Demo Reference Architecture.
Note
FX Transaction Lifecycle States describe the logical processing condition of transaction information. They do not redefine the operational lifecycle states of FX logical Nodes.
Example
An FX Transaction Candidate enters Validation Pending after intake. It enters Validation Passed when the FX Validation Node produces a successful FX Validation Result.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.