| |
| fxdemo:03-part:11-fx-transaction-and-contract-lifecycle-model:11-1-overview:start [2026/07/14 18:22] – created owen | fxdemo:03-part:11-fx-transaction-and-contract-lifecycle-model:11-1-overview:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| This model distinguishes candidate transaction information, validated transaction information, semantically interpreted transaction information, [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state|FX Contract State]], computed [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_cash-flow_obligation|FX Cash-Flow Obligation]]s, [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_decision|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. | This model distinguishes candidate transaction information, validated transaction information, semantically interpreted transaction information, [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state|FX Contract State]], computed [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_cash-flow_obligation|FX Cash-Flow Obligation]]s, [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_decision|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, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] topic, [[dido:99_annexes:annex-b-terms-and-definitions:r:rest|REST]] resource, or runtime persistence mechanism. Implementation profiles select those realisation mechanisms. | 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, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] topic, [[dido:99_annexes:annex-b-terms-and-definitions:r:rest|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. | Figure 11-1 summarises the logical lifecycle progression used by the FX Demo Logical Profile. |