Version, Evidence, and Claim Ledgers
A research audit begins by fixing the object under review. Titles, filenames, and repository labels can survive substantive revisions, so each source needs a version record. A claim ledger then connects quoted propositions to assumptions, proof locations, code paths, data inputs, and the auditor's residual conclusion.
- Source hierarchy
- Version records
- Claim units
- Assumption tables
- Residual conclusions