Validation-controlled transitions depend on the result of logical validation.
The FX Validation Node produces an 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, FX Validation Result, validation rule version, producing 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 FX Validation Result supports that transition.
FX lifecycle transition governed by an FX Validation Result.
Specialization of FX Validation Result from Section 9.4, Structural Validation Role from Section 7.3, Logical Assertion from Part 2, Section 8.8, and Traceability from Part 1, Section 7.10; generalised from FX validation and transaction-lifecycle material in the original FX Demo Reference Architecture.
Validation-controlled transitions do not prescribe a validation engine, schema validator, rules engine, test framework, database status update, or runtime workflow.
An FX Transaction Candidate moves from Validation Pending to Validation Passed when the FX Validation Node produces an FX Validation Result confirming conformance with required logical validation expectations.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.