====== FX Evidence Traceability ======

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

===== Discussion =====

FX Evidence Traceability relates FX logical profile elements and FX logical interactions to the [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations that later implementation, deployment, testability, and evidence plans satisfy.

FX Evidence Traceability does not create runtime [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] in Part 3. It identifies what later parts need to evidence. It connects claims about FX logical behaviour to the FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]], endpoints, information structures, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], interactions, governance constraints, lifecycle states, audit records, provenance records, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships that support those claims.

FX Evidence Traceability prepares Part 5 to define deployment evidence, captured messages, logs, status records, audit records, provenance records, replay results, test results, configuration snapshots, review records, and evidence packages.

===== Definition =====

//Traceability relationship connecting FX logical profile elements and FX logical interactions to evidence expectations for later implementation, deployment, testing, and review.//

===== Source =====

Specialisation of [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_evidence_traceability|Logical Evidence Traceability]] from Part 2, Section 12.8, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] from Part 1, Section 7.9, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from Part 1, Section 7.10; generalised from FX acceptance evidence, audit, provenance, replay, reconstruction, and runtime evidence material in the original FX Demo Reference Architecture.

===== Note =====

FX Evidence Traceability identifies evidence expectations. It does not prescribe evidence files, logs, screenshots, dashboards, repositories, test tools, or runtime capture mechanisms.

===== Example =====

The Validate FX Transaction Candidate pattern includes an evidence expectation that later parts capture validation inputs, [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_result|FX Validation Results]], the validation rule version, the producing [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] identity, timestamp, and a provenance reference.

----

<WRAP centeralign>

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

</WRAP>