What should I know about why Tradour keeps an audit trail?
An audit trail preserves sources, versions, transformations, decisions and corrections so a result can be reproduced and its history understood. It prevents later knowledge from silently rewriting earlier claims.
3 minute readReviewed 16 August 2026Beginner level
Make it click
Keep every signed revision
A building plan remains trustworthy when each revision is dated and earlier versions remain available. Replacing the old sheet destroys the reason a decision was made.
Now put that into markets
Here is the idea in its proper setting
Tradour links immutable sources to parser versions, derived artifacts, findings, reviews and prospective events. Corrections append rather than erase.
01
How it works
Checksums identify source bytes; manifests record lineage; identifiers connect records across layers. Access to private sources remains restricted.
02
How to read it carefully
Follow the chain from public claim back to approved aggregate and methodology. Confirm that versions and dates reconcile.
Go deeperThe important limit+
03
The important limit
Logging everything without structure can expose secrets or become unusable. Least privilege and retention boundaries remain part of audit design.
Takeaway
The useful version
Preserve what changed, when, why and from which source.