FX Evidence Traceability

Return to Terms and Definitions

FX Evidence Traceability relates FX logical profile elements and FX logical interactions to the Evidence expectations that later implementation, deployment, testability, and evidence plans satisfy.

FX Evidence Traceability does not create runtime Evidence in Part 3. It identifies what later parts need to evidence. It connects claims about FX logical behaviour to the FX logical Nodes, endpoints, information structures, Runtime Planes, interactions, governance constraints, lifecycle states, audit records, provenance records, and 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.

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

Specialisation of Logical Evidence Traceability from Part 2, Section 12.8, Evidence from Part 1, Section 7.9, and 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.

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

The Validate FX Transaction Candidate pattern includes an evidence expectation that later parts capture validation inputs, FX Validation Results, the validation rule version, the producing Node identity, timestamp, and a provenance reference.