Audit and Provenance State Record

Return to Terms and Definitions

Audit and provenance state records preserve the logical history of FX lifecycle processing.

The FX Audit and Provenance Node records or relates transaction intake, validation outcomes, semantic assertions, contract state transitions, cash-flow computation outputs, policy decisions, release packages, replay requests, reconstruction results, Node participation, endpoint participation, rule versions, model versions, timestamps, and Evidence expectations.

Audit and provenance state records support review, reconstruction, replay, accountability, lineage, and defensibility. They allow reviewers to understand how an FX transaction moved from candidate information to a validated record, an FX Semantic Assertion, an FX Contract State, a computed FX Cash-Flow Obligation, an FX Policy Decision, an FX Release Package, an FX Replay Result, or a reconstructed output.

Audit and provenance state records preserve lifecycle history without prescribing a database, log file, event store, graph store, provenance repository, ledger, Evidence repository, or runtime persistence mechanism.

Audit and provenance records preserving the logical history of FX lifecycle processing.

Specialization of FX Audit Record from Section 9.10, FX Provenance Record from Section 9.11, FX Audit and Provenance Node from Section 6.8, Logical Information Lineage from Part 2, Section 8.10, Evidence from Part 1, Section 7.9, and Traceability from Part 1, Section 7.10; generalised from audit, provenance, persistence, replay, reconstruction, and evidence material in the original FX Demo Reference Architecture.

Audit and provenance state records support Evidence, but they do not replace it. Evidence supports claims; audit and provenance records preserve relationships and history needed to evaluate those claims.

An FX Provenance Record links an FX Release Package to the FX Policy Decision, FX Cash-Flow Obligation, FX Contract State, FX Validation Result, FX Transaction Candidate, producing Nodes, rule versions, timestamps, and Evidence expectations.