====== FX Transaction Lifecycle State ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]

===== 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, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], governance, replay, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|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 [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] defined here.

===== Definition =====

//FX logical lifecycle condition associated with FX transaction information during processing, release, audit, provenance, replay, or reconstruction.//

===== Source =====

Specialization of [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_instance|Logical Data Structure Instance]] from Part 2, Section 8.3, [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_record|Logical Record]] from Part 2, Section 8.9, [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_information_lineage|Logical Information Lineage]] from Part 2, Section 8.10, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|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 [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]].

===== Example =====

An FX Transaction Candidate enters **Validation Pending** after intake. It enters **Validation Passed** when the [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_node|FX Validation Node]] produces a successful [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_result|FX Validation Result]].

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>