11.1 Overview

Go To FX Transaction and Contract Lifecycle Model

The FX Transaction and Contract Lifecycle Model defines the FX-specific lifecycle states and state-transition responsibilities used by the FX Demo Logical Profile.

This model distinguishes candidate transaction information, validated transaction information, semantically interpreted transaction information, FX Contract State, computed FX Cash-Flow Obligations, FX Policy Decision state, and audit/provenance records. It preserves the difference between a transaction input, a validation outcome, an interpreted contract, a contract lifecycle state, a computed obligation, and a release decision.

The FX Transaction and Contract Lifecycle Model remains platform-independent. It does not prescribe a state-machine implementation, workflow engine, database status field, event store, rules engine, orchestration mechanism, API, DDS topic, REST resource, or runtime persistence mechanism. Implementation profiles select those realization mechanisms.

Figure 11-1 summarises the logical lifecycle progression used by the FX Demo Logical Profile.

FX Transaction Candidate
└── Validated FX Transaction
└── Semantically Interpreted FX Transaction
└── FX Contract State
└── FX Cash-Flow Obligation
└── FX Policy Decision
└── FX Release Package

Figure 11-1: FX logical lifecycle progression from transaction candidate to release package.

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