A tracing result without a source trail is difficult to defend or challenge. Reviewers need to know which statement supported which ledger row, whether the exported file matches the generated snapshot, and which assumptions were in force when the workpaper was produced.
What provenance covers
Provenance in Exit Protocol is practical, not theatrical: selected source files, extracted transaction rows, calculation inputs, and export-time integrity references are kept adjacent to the review workflow — not buried in a separate system.
Statements, exports, and exhibits selected for the matter.
Material ledger rows and workpaper lines reference their source context.
Snapshot SHA-256 at export and exact file-hash verification for generated exports.
Provenance workflow
Keep uploaded statements and exports tied to the accounts and periods under review.
Connect material ledger entries to the records that produced or support them.
Capture a snapshot integrity reference when the workpaper is generated.
Allow exact file-hash matching at /verify/ for generated exports.
Deterministic math versus assistive preparation
LIBR replay and ledger totals are deterministic. Document preparation steps may use bounded assistive tooling, but those steps do not alter the tracing math or substitute for counsel judgment. Any assistive output remains draft material for human review.
Strong provenance
Source list, material rows, strategy disclosure, snapshot hash, and a conservative verification path.
Weak provenance
Exported PDF with no source references, no integrity surface, and no way to test whether the file changed.
Provenance reduces drift between conclusion and record. It does not eliminate evidentiary disputes — reviewers still decide authenticity, completeness, and litigation use.