| Both sides previous revision Previous revision Next revision | Previous revision |
| public:99_annexes:annex-b-terms-and-definitions:v:validation-controlled_transitions [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:v:validation-controlled_transitions [2026/09/16 14:50] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| | ====== Validation-Controlled Transition ====== |
| |
| | [[public:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]] |
| | |
| | ===== Discussion ===== |
| | |
| | Validation-controlled transitions depend on the result of logical validation. |
| | |
| | The [[private:01-fxdemo:99-annexes:annex-b-terms-and-definitions:fx_validation_node|FX Validation Node]] produces an [[private:01-fxdemo:99-annexes:annex-b-terms-and-definitions:fx_validation_result|FX Validation Result]]. That result determines whether an FX Transaction Candidate proceeds to semantic interpretation, is returned for correction, is rejected, or supports an audit/provenance record explaining the validation failure. |
| | |
| | A validation-controlled transition identifies the input transaction candidate, [[private:01-fxdemo:99-annexes:annex-b-terms-and-definitions:fx_validation_result|FX Validation Result]], validation rule version, producing [[private:01-fxdemo:99-annexes:annex-b-terms-and-definitions:fx_validation_node|FX Validation Node]], timestamp, resulting lifecycle state, and provenance reference. |
| | |
| | Validation-controlled transitions preserve the distinction between candidate information and accepted transaction information. A candidate transaction does not become a validated FX Transaction Record until the [[private:01-fxdemo:99-annexes:annex-b-terms-and-definitions:fx_validation_result|FX Validation Result]] supports that transition. |
| | |
| | ===== Definition ===== |
| | |
| | //FX lifecycle transition governed by an FX Validation Result.// |
| | |
| | ===== Source ===== |
| | |
| | Specialization of [[private:01-fxdemo:99-annexes:annex-b-terms-and-definitions:fx_validation_result|FX Validation Result]] from Section 9.4, [[public:99_annexes:annex-b-terms-and-definitions:s:structural_validation_role|Structural Validation Role]] from Section 7.3, [[public:99_annexes:annex-b-terms-and-definitions:l:logical_assertion|Logical Assertion]] from Part 2, Section 8.8, and [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from Part 1, Section 7.10; generalised from FX validation and transaction-lifecycle material in the original FX Demo Reference Architecture. |
| | |
| | ===== Note ===== |
| | |
| | Validation-controlled transitions do not prescribe a validation engine, schema validator, rules engine, test framework, database status update, or runtime workflow. |
| | |
| | ===== Example ===== |
| | |
| | An FX Transaction Candidate moves from **Validation Pending** to **Validation Passed** when the [[private:01-fxdemo:99-annexes:annex-b-terms-and-definitions:fx_validation_node|FX Validation Node]] produces an [[private:01-fxdemo:99-annexes:annex-b-terms-and-definitions:fx_validation_result|FX Validation Result]] confirming conformance with required logical validation expectations. |
| | |
| | ---- |
| | |
| | <WRAP centeralign> |
| | |
| | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| | |
| | </WRAP> |